[exporterhelper] Make the in-memory and persistent queues more consistent #5764
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.
Description:
This change is part of an effort to enable the persistent queue by default, without requiring the
enable_unstable
tag. Right now, there are minor inconsistencies between the queue behaviours, and this PR removes them. The intent is for enabling the persistent queue in the build by default to not change any behaviour.More specifically:
requeuing
feature, though it's not enabledThis was originally part of #5711, which ended up doing too many things at once.
Link to tracking Issue: N/A
Testing:
Added some tests for parts of the persistent queue that weren't originally covered.