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

cannot read BUFR message if sections total length differs message's #57

Open
vsouvan opened this issue Apr 19, 2020 · 1 comment
Open

Comments

@vsouvan
Copy link
Collaborator

vsouvan commented Apr 19, 2020

When the total of all section's encoded length is different than the length of BUFR message as encoded in section 0,
as found in some badly encoded messages.
S0.length + S1.length + S2.length + S3.length + S4.length + S5.length < Total length of BUFR message set in Section 0

The bufr_read_message() function is unable to adapt and read the message anyway,
even if it contains all valid data but filled at the end by unused spaces, that is when the BUFR message is longer than it should be.


Imported from Launchpad using lp2gh.

@vsouvan
Copy link
Collaborator Author

vsouvan commented Apr 19, 2020

(by vanh-souvanlasy)
Fixed with rev. 136 in trunk

@vsouvan vsouvan added this to the 0.8.2b4 milestone Apr 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant