Skip to content

Conversation

@Raunaque97
Copy link
Contributor

This PR adds a unique sequencer.id to a sequencer instance and includes it in all task payloads.
So the Flow class can now filters out responses from old sequencer instances.

Fixes #314

@Raunaque97 Raunaque97 marked this pull request as ready for review November 12, 2025 06:29
@Raunaque97 Raunaque97 requested a review from rpanic November 12, 2025 06:29
removed .vscode/launch.json
Copy link
Member

@rpanic rpanic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved given fix of the one new comment


// Drain all task queues to clear stale tasks from previous sequencer instances
if (this.container.isRegistered("TaskQueue")) {
const taskQueue = this.container.resolve<TaskQueue>("TaskQueue");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought I added a comment here but apparently didn't (please say if we already talked about it).
But I'd much rather see this logic here implemented in the start() function that the TaskQueue implements (SequencerModule requires that anyways, and it is automatically called by the sequencer during startup)

@Raunaque97 Raunaque97 requested a review from rpanic November 18, 2025 07:29
@Raunaque97 Raunaque97 merged commit 9a10a1d into develop Nov 18, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add unique sequencer id to job payload

3 participants