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

Repeating group fields out of order #34

Open
aozeahj opened this issue Nov 5, 2022 · 0 comments
Open

Repeating group fields out of order #34

aozeahj opened this issue Nov 5, 2022 · 0 comments
Assignees
Labels
Bug Behavior not matching expected

Comments

@aozeahj
Copy link

aozeahj commented Nov 5, 2022

Describe the bug

"Repeating group fields out of order (group 268: template is wrong or delimiter 269 not found: expected 2 groups, but found 1)"

To Reproduce
First, I send a fix message with msgType = V to subscribe to the exchange rate data in both bid and offer directions

Then I successfully received the msgType = W message returned by the bank, and the message has data in both bid and offer directions, and the message is correct

However, when the program runs to "marketdatasnapshotfullrefresh.FromMessage(message)" and parses out the message data of msgType = W, and then calls "marketDataMsg.GetNoMDEntries() ", an error occurs, and the error message is as shown above.

Expected behavior
Logically, there should be no error, and the exchange rate data in both bid and offer directions can be successfully obtained.

system information:

  • OS: Mac
  • Go version: Go 1.16.5
  • QF/Go Version v0.6.0

Additional context
I read the ParseMessage() method of the message. In this method, the message data is directly parsed into the Body field, and the Body is a map data structure. It does not support repeating groups. Is it caused by this?

@aozeahj aozeahj added the Bug Behavior not matching expected label Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Behavior not matching expected
Projects
None yet
Development

No branches or pull requests

2 participants