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

bug in EnableLastMsgSeqNumProcessed: When a logon response has a too-high seq no, the next message will set 369 incorrectly #942

Open
gbirchmeier opened this issue Mar 7, 2025 · 0 comments
Assignees

Comments

@gbirchmeier
Copy link
Member

gbirchmeier commented Mar 7, 2025

Wrote a UT to demonstrate. See my branch commit that tags this issue.

@gbirchmeier gbirchmeier self-assigned this Mar 7, 2025
gbirchmeier added a commit to gbirchmeier/quickfixn that referenced this issue Mar 7, 2025
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

No branches or pull requests

1 participant