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

[FIXED] JetStream: jsConsumerConfig.Name was not unmarshal'ed #599

Merged
merged 1 commit into from
Oct 5, 2022

Conversation

kozlovic
Copy link
Member

@kozlovic kozlovic commented Oct 5, 2022

The new configuration Name in jsConsumerConfig could be set when calling js_AddConsumer, but when getting the jsConsumerInfo response (from that call or any js_GetConsumerInfo, the Name was present in jsConsumerInfo, but was not in the Config field (a jsConsumerConfig). Although I am not sure this is needed, making sure that we unmarshal properly.

Signed-off-by: Ivan Kozlovic [email protected]

The new configuration `Name` in `jsConsumerConfig` could be set
when calling `js_AddConsumer`, but when getting the `jsConsumerInfo`
response (from that call or any `js_GetConsumerInfo`, the `Name`
was present in `jsConsumerInfo`, but was not in the `Config` field
(a `jsConsumerConfig`). Although I am not sure this is needed,
making sure that we unmarshal properly.

Signed-off-by: Ivan Kozlovic <[email protected]>
@kozlovic kozlovic requested a review from aricart October 5, 2022 22:12
Copy link
Member

@aricart aricart left a comment

Choose a reason for hiding this comment

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

LGTM

@kozlovic kozlovic merged commit 96eecca into main Oct 5, 2022
@kozlovic kozlovic deleted the js_cons_config_name_unmarshal branch October 5, 2022 22:18
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