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

Fix sequence number bug when storage fails #432

Merged
merged 3 commits into from
Nov 9, 2023

Conversation

letian0805
Copy link

If update sequence number cache before store it to mongodb, sql or file, and then get an error, will cause the sequence number to be discontinuous. So, store sequence number before update cache.

@ackleymi
Copy link
Member

ackleymi commented May 8, 2023

@letian0805 please rebase, this is something I am interested in seeing get merged.

@letian0805 letian0805 force-pushed the fix/sequence_number_bug branch 2 times, most recently from 276a3dd to 9a26a53 Compare May 16, 2023 02:32
@letian0805
Copy link
Author

@letian0805 please rebase, this is something I am interested in seeing get merged.

@ackleymi The performance optimization parts are incompatible with existing unit tests, I'll break them out separately. Fix the sequence number bug first.

@letian0805 letian0805 force-pushed the fix/sequence_number_bug branch from 35f1be2 to b85ce2b Compare October 30, 2023 10:46
@ackleymi ackleymi merged commit 5290cae into quickfixgo:main Nov 9, 2023
39 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.

2 participants