Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ordered consumer start time fix #424

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

mtmk
Copy link
Collaborator

@mtmk mtmk commented Mar 1, 2024

When initial request delivery policy is by time
all subsequent request should still start by
sequence and reset start-time field to avoid
errors returned by server.

When initial request delivery policy is by time
all subsequent request should still start by
sequence and reset start-time field to avoid
errors returned by server.
@mtmk mtmk requested a review from caleblloyd March 1, 2024 14:27
Copy link
Collaborator

@caleblloyd caleblloyd left a comment

Choose a reason for hiding this comment

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

LGTM

@mtmk mtmk added this to the 2.1.3 milestone Mar 4, 2024
mtmk added a commit that referenced this pull request Mar 11, 2024
@mtmk mtmk mentioned this pull request Mar 11, 2024
@mtmk mtmk merged commit 92f71ce into main Mar 11, 2024
10 checks passed
@mtmk mtmk deleted the 420-ordered-consumer-big-gap-between-messages branch March 11, 2024 10:40
mtmk added a commit that referenced this pull request Mar 12, 2024
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.

NatsJSConsume timedout when using Ordered Consumer (big gap between messages)
2 participants