Tormod Erevik Lea
Tormod Erevik Lea
It looks like we're hitting https://issues.apache.org/jira/browse/KAFKA-9543, which is causing the `ErrOffsetOutOfRange` errors. The question still remains if Burrow should handle the error more gracefully than crashing.
Thanks for the report. I'll try to look into this if I have some available time (together with your other PRs), but it may take a while.
Superseded by #67.
Just released `v0.15.0` with #67 included. @cloudlena, if you're still interested, you can check if that change solves your issue.
> I believe [the documentation](https://developer.garmin.com/fit/protocol/) says the elevation (like any numeric value) may have a scale and offset (those may be 1 and 0 respectively), It is my understanding that...
I'll need to take a closer look, but you're sure field def numbers are correct? (190, 191 and 192.)
They'll need to match the field def numer they're encoded with in the file. It looks like these are undocumented/"hidden", and not present in the SDK specification. What did you...
Data Developer Fields are not supported fully be this libary yet. It supports parsing files containing them (i.e. parse files containing them without crashing), but they're not parsed/available yet. I'm...
Hi. Thanks for the links regarding Coros files. We would need to add a more permissive parsing mode to allow such "bugs".
Thanks, I will take another look.