[bug] workouts from before 0.10.0 are not properly updated with latest changes

[Thovi98]

Checklist

• [x] Describe the bug.
• [ ] Copy of the output/log.
• [ ] Include your .env file.
• [x] Steps to Reproduce
• [ ] The exact command that failed. This is what you typed at the command line, including any options.
• [x] FitTrackee version, this is reported by pip show fittrackee
• [x] Operating System and Python Version
• [x] Installed Python packages

Describe the bug

Hello, thank you for this great update! I’ve upgraded my prod instance from latest 0.9 version, it worked great.

But the additional infos are not updated on already added workouts, next to the map. If I add a new workout, those additions are correctly shown.

The additions: source, cadence and heart rate.

The graph is well updated for older workouts.

YunoHost 12 (Debian 12) with latest pypi version (0.10.0)

Copy of the output/log

No response

Include the .env file

No response

To Reproduce

No response

FitTrackee Version

0.10.0

Python Version

3.11

FitTrackee installation method

From PyPI

Operating System

GNU/Linux

Python Packages

No response

[SamR1]

Hi,

Thanks for the feedback.

Source and the max and average values for heart rate and cadence are stored in database on file upload. The workout uploaded before v0.10.0 are not updated, so theses values are missing and not displayed.

The values for the chart are read from the gpx file (for the moment, this may change in a next version), and appear up to date.

I forgot to mention this in the documentation :/

[Dryusdan]

Hi o/

This is possible to add a new API endpoint to resend activity ? Like you have your activity and an application (like mine o:) ) can resend old GPX to reprocess in fittrackee ? :) (other can be delete and recreate I think, but some parameter in fitrackee (like commute biking) will be lost.

[SamR1]

Hi,

Like you have your activity and an application (like mine o:) ) can resend old GPX to reprocess in fittrackee ?

The same gpx file? or an updated one?

If it is the same, I can add a refresh button/endpoint to recalculate some data from the existing gpx file and fetch weather if missing for instance.

[Dryusdan]

I think the same, I thought that once GPX is processed it was deleted. If it already stored, it can be cool to recalculate all 😇

[SamR1]

Unfortunately, recalculating all sessions will not be possible via an endpoint due to the potential volume of data.

For information, I'm currently working on storing GPX file data in a database to ease implementation of some new features (and avoid recalculating some values ​​when the workout is displayed). In this case, it will be necessary to update/recalculate all workouts (this will be done via a script/CLI command). The refresh button will be useful in this case, as the original file will no longer be read again to display the workout, but will still be present.

Maybe in a future version it will be possible to refresh multiple workouts at the same time (like for bulk modification), but there will always be a limit on the number of files updated.

[SamR1]

Hi,

Source and the max and average values for heart rate and cadence are stored in database on file upload. The workout uploaded before v0.10.0 are not updated, so theses values are missing and not displayed.

The values for the chart are read from the gpx file (for the moment, this may change in a next version), and appear up to date.

This behavior has not changed, but a refresh button is now available in v0.12.0 to update the workout, as well as a CLI command.