Track if EvalCtxt has been tainted, make sure it can't be used to make query responses after #110618
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.
Just some additional protection against missing probes or strange candidate assembly behavior in the new solver.
For background, we don't ever want to call
evaluate_added_goals_and_make_canonical_response
if a previous call totry_evaluate_added_goals
has bailed withNoSolution
, since our nested goals are left in an undefined state at that point. This most commonly suggests a missingEvalCtxt::probe
, but could also signify some other shenanigans like dropping aQueryResult
on the floor without properly?
'ing it.r? @lcnr