Bug: Can't update inside of a metadata context when iterating over a different query #541
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.
Reproduction test (assuming a datasource with 1.txt..5.txt datapoints):
Right now this is failing, because
res == ["old", None, None, None, None]
Happens because
datasource[field].is_null().all()
ends up creating a new datasource object, and so closing the original datasource's context doesn't end up uploading the implicit datapoints.To fix this I extracted all implicit contexts in a global dictionary keyed by the datasource ID, that way no matter if you're doing subqueries, you're always getting the metadata context of this datasource that ends up being uploaded at some point.
Made sure that all the backend E2E tests are passing after this.