fix(query): Make query serialization thread-safe #198
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.
Serializing multiple queries in multiple threads is not thread safe. The
PRINTER
global is reused by the Query serializer across these requests and maintains a localTranslator
in thetranslator
classvar.This would be fine if the
translator
were never mutated. However, thevisit
function temporarily mutates thetranslator
usingentity_aliases()
.If multiple queries are being serialized concurrently, there are bad inverleavings of this code that result in invalid queries.
This can be reproduced with this diff and some long running queries issued in a batch (example):
When we're lucky, the output shows that the
translator
'suse_entity_aliases
field is not mutated by multiple threads. When we're unlucky, it is.Good
Bad