Bug: sentry tracing - don't assume query.selected_operation is defined #5433
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.
I observed an error in my production application where
query.selected_operation
was nil. As best I can tell, this was due to a query that looks to me to be invalid, but was executed with some partial success. I recognize the details here are light.A simplified version of the query that generated this is:
The backtrace was:
I am still surprised this query was not rejected, so I am not sure exactly how to write a test that would demonstrate this. Please advise on any other info I can provide.