Closed al0git closed 2 years ago
Looks like you are still using an older version of fit4ruby. Please make sure you only have version 3.9.0 installed as required by the postrunner gem file.
Thanks for your quick answer.
You are right, I still had v3.0 and v3.9 of fitruby. Fixed this and works like a charm.
Thanks.
On 2022-03-17 21:09, Chris Schlaeger wrote:
Looks like you are still using an older version of fit4ruby. Please make sure you only have version 3.9.0 installed as required by the postrunner gem file.
— Reply to this email directly, view it on GitHub https://github.com/scrapper/postrunner/issues/32#issuecomment-1071343543, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARRHDQBJRO2TJH4XG5YQWHLVAOGPNANCNFSM5Q6NCVLQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.
Hello,
I'm running Debian testing and switched to ruby 3.0. This was the occasion to update my old postrunner setup to 1.0.5. I then tried to import all my .FIT files. When I try to import even a single file (e.g postrunner -v import C2KB2851.FIT), postrunner loops forever and the memory the process is using is increasing regularly. I can stop postrunner using ^C and get the following message (maybe it can help locate the loop)
The following patch workarounds the problem (just does not use the recent sweat estimation feature ?).
Don't hesitate if you need more information.
Thanks.