8000 strange error message · Issue #43 · tormoder/fit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

strange error message #43

8000
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.

Sign up for GitHub

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

Jump to bottom
Closed
hneemann opened this issue Jan 7, 2020 · 4 comments · Fixed by #54
Closed

strange error message #43

hneemann opened this issue Jan 7, 2020 · 4 comments · Fixed by #54

Comments

@hneemann
Copy link
hneemann commented Jan 7, 2020 •
edited
Loading

I get the following error message when importing a fit file:

parsing definition message: validating Session failed: field 6: size (4) is greater than size of profile base type BaseSint32 (4)

which to me seems like stating 4>4

This is the file causing the problem.
@tormoder
Copy link
Owner
tormoder commented Jan 8, 2020

Thanks, there was an error in the error message. I've fixed it, expanded it and now it says:

parsing definition message: validating Session failed: field 6: size 4 for BaseSint32 as base type in definition message is greater than size 1 for BaseEnum as base type from profile

I think the reason is that it expects an enum (sub_sport) for field 6 of the Session message. That's what is described in the profile and an enum has size 1.

The library may also do something wrong. I'll try to take a look later.

@hneemann
Copy link
Author
hneemann commented Jan 8, 2020

The library may also do something wrong. I'll try to take a look later.

I had that feeling too. I played around with the file a bit, and I think it's fine.

@bpg
Copy link
Contributor
bpg commented Dec 27, 2020

I have the same error as above, will try to figure out what's going on there. My activity is from a Garmin device as well.

@bpg
Copy link
Contributor
bpg commented Jan 2, 2021

This happens when a message has more than 85 fields (255/3). The fix is coming...

@bpg bpg mentioned this issue Jan 2, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for large messages
3 participants
2DDD @bpg @hneemann
0