Tom Goetz

Looks like that option is only in 3.9+. I will look into other options: > Changed in version 3.9: Add --upgrade-deps option to upgrade pip + setuptools to the latest...

> I got a new development environment up, but it appears to try for a version of fitfile that is not available. Is there a way to get the newer...

UNIQUE constraint failed: files.name => '6078279536_ACTIVITY.fit' stack is: ` File "/home/max/GarminDB/fit_file_processor.py", line 50, in __write_generic function(fit_file, message.fields) File "/home/max/GarminDB/fit_file_processor.py", line 232, in _write_user_profile_entry self._write_attributes(timestamp, message_fields, attribute_names) File "/home/max/GarminDB/fit_file_processor.py", line 208,...

I saw those logs in the garmin.log in the bug report. It's not a matter of more logging, it's a matter of logging at the right time. The issue is...

Use the program "patch" For instructions "man patch".

This isn't a GarminDB issue. You need to debug your installation on why numpy isn't installing correctly. Numpy is a separate package that is a dependency of GarminDb.

Sorry for the slow response. I've been otherwise occupied. The problem is that your DB does not have an entry in the Attributes table for measurement_system. Those entries come from...

Can you try with the develop branch and see if it fixes you issue?

The capitalization is not consistent between watches. I will think about a solution.

Looks like your on Windows. What happens when you run it from a command prompt like `C:\Users\lucas\anaconda3\Bin\python.exe C:\Users\lucas\anaconda3\Lib\site-packages\garmindb\garmindb_cli.py --all --download --import --analyze` Is C:\Users\lucas\anaconda3\Lib\site-packages\garmindb\garmindb_cli.py marked as executable? Sounds similar to...