Skip to content

Use FieldException instead of InvalidMessage for bad repeating group count - #1362

Open
philipwhiuk wants to merge 1 commit into
quickfix-j:masterfrom
philipwhiuk:qfj1360
Open

philipwhiuk wants to merge 1 commit into
quickfix-j:masterfrom
philipwhiuk:qfj1360

Conversation

@philipwhiuk

@philipwhiuk philipwhiuk commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Change from InvalidMessage to FieldException

Fixes #1360

@chrjohn chrjohn changed the title Use FieldException instead of InvalidMessage for bad repeating group count Use FieldException instead of InvalidMessage for bad repeating group count Oct 28, 2026
@chrjohn

chrjohn commented Oct 28, 2026

Copy link
Copy Markdown
Member

@philipwhiuk thanks for the PR. Seems unit tests need adapting since now a Reject is sent instead of considering the message as garbled...

@Johnny-Kao Johnny-Kao left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@philipwhiuk philipwhiuk

Thanks for the fix! I had a quick look at the CI failures.

The two failing tests seem to just need updated expectations for the new Reject behavior.

I also noticed that testRepeatingGroupCountWithNonIntegerValues might now pass without actually checking anything, since the exception is stored rather than thrown.

Might be worth checking the reject reason/tag there, and confirming the behavior with RejectInvalidMessage=N as well.

Hope this helps!

This branch has not been deployed

No deployments
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.

Should we treat bad repeating group counts as IncorrectDataFormat instead of InvalidMessage

3 participants