feat(queue): fast_forward_collaborative_group#80
Merged
Conversation
louisponet
approved these changes
May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds an opt-in way for a collaborative group to join at the producer's current write head instead of replaying whatever is still in the ring.
A fresh collaborative consumer's
init_collaborativecallsacquire_next_slotfrom a zero-initialised group cursor; the cursor immediately getsSpedPastand falls back toacquire_earliest_available_slot, landing atcount - queue.len()— i.e. a full ring of backlog. That is correct for groups whose payload outlives the queue, but it's wrong when the payload references data with a tighter lifetime (e.g. an external arena that recycles independently). Replaying the backlog there produces stale references and noisy warnings.Queue::fast_forward_collaborative_group(label)advances the group cursor viafetch_max(self.count()), allocating the slot if needed. Exposed onFluxSpinefor any field withAsRef<SpineQueue<T>>.Safety: must be called once, before any group member starts consuming. After a member's
acquire_next_slothas run,fetch_maxcan overshoot already-claimed positions and silently drop messages produced in the gap. Documented on the API.Tests: single-consumer skips backlog; 4-consumer group sees every post-fast-forward message exactly once.