"Richard (MQ)" <osl2...@gmail.com> writes: > On 30/03/18 20:31, Arto Jantunen wrote: >> "Richard (MQ)" <osl2...@gmail.com> writes: >>> Hi, >>> >>> Good to see that the pytrainer project is not dead - I've been using it for >>> a >>> couple of years now with my Garmin Forerunner 15 watch. >>> >>> I recently re-installed pytrainer after upgrading my PC to opensuse 42.3, >>> and >>> I'm now using v1.12 - it fails importing FIT files, including some that >>> pytrainer 1.09 could read OK. I'm using garmintools-0.10 as previously. >>> >>> Everything is as expected until in "Modify details before importing" the >>> activity metadata is shown correctly, but clicking on "OK" just blinks the >>> screen and doesn't return to "Import" window, the log shows >>> sqlalchemy.exc.StatementError: (exceptions.ValueError) could not convert >>> string to float... >>> >>> Is this something connected to the database front-end change that came with >>> 1.12? >>> >>> PS also tried master from GIT today, same symptoms >> >> Yes, this is most likely related to those changes. There are many areas >> of the code that used to be rather imprecise with the data types used >> (using "" instead of None and such), and the new SQLAlchemy based code >> cares about this much more than the previous version which built it's >> SQL statements using string concatenation. I fixed one case like this >> just today in commit a1655db8ffb7, but it seems like you are probably >> hitting different one. >> >> I assume that the full traceback doesn't have anything useful in it >> (everything happens within SQLAlchemy code)? The previous case I saw was >> like that, and needed to be debuggeg pretty manually. Is it possible for >> you to send me a copy of a file which reproduces this (off list if you >> are ok with sharing the file with me but not the world)? >> >> I'm planning to release 1.12.1 with a number of bug fixes soonish, it >> would be great to get this one fixed as well. >> > > Hi Arto > > Thanks, I will send one of the FIT files off-list. > > I'm not sufficiently familiar with Python / sqlite debugging to know how best > to produce a traceback, is running with -d and capturing the console output > any use? All I see is a long line starting with "could not convert string to > float" and listing the parameters of that database transaction.
I ran into a similar problem myself, and ended up with this commit: https://github.com/viiru-/pytrainer/commit/8825750ddb625ba9409a7ff6dccaca56a9627c54 Does applying it happen to fix this problem you are seeing? -- Arto Jantunen ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
