fix: handle null subgraph schema check results #2639
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some customers reported that they get the
E005
error when runningrover subgraph check
, even though the schema check passes on Studio. I managed to reproduce it and realized that this error can happen if the operations check task takes too long. So, when Rover tries to fetch the results for the workflow, the operations check hasn’t finished yet. This behavior is also clearly documented in the Platform API schema.To resolve this timing issue, we've modified the code so it doesn't throw
MalformedResponse
. This change also aligns with howrover graph check
handles null schema check results:rover/crates/rover-client/src/operations/graph/check_workflow/runner.rs
Lines 108 to 123 in fe86b2c