Skip to content

fix: subscriber idempotency handling - #20

Merged
mm-zacharydavison merged 4 commits into
mainfrom
mm-derek/fix/Idempotent_no_still_retries_processing_after_failure
Aug 18, 2026
Merged

mm-zacharydavison merged 4 commits into
mainfrom
mm-derek/fix/Idempotent_no_still_retries_processing_after_failure

Conversation

@mm-derek

Copy link
Copy Markdown
Collaborator

Subscriber idempotent setting was not working for both cases:

  • Non-idempotent subscriber throws error
    • Was retrying even when idempotent set to no
  • Non-idempotent subscriber crashes
    • Was retrying even when idempotent set to no

@mm-derek mm-derek self-assigned this Aug 17, 2026
await matador.start();

// Wait for processing
await matador.waitForIdle(10_000);

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This seems flaky and I don't think related to the timeout value actually. Maybe a race condition with the isIdle check actually completing before processing has started?
Needs some more thought.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

given it's polling for idle rather than just waiting for 10_000 i don't think it's too bad

@GuillaumeDecMeetsMore GuillaumeDecMeetsMore left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@mm-zacharydavison mm-zacharydavison left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@mm-zacharydavison
mm-zacharydavison merged commit e109ff5 into main Aug 18, 2026
4 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.

3 participants