You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My guess is this is due to improperly parsing the date, which in my case is in the Slovenian locale.
I'm also guessing this issue can be resolved by forcing a specific locale for exports, instead of using the system-defined one (2022-06-25 16:05:42-16:05:48 seems much more readable in exports to me anyway).
When imported the result looks like this:
The text was updated successfully, but these errors were encountered:
My guess would have been that there's no separation between the timer (01:35:51) and the day/date (Tue, 17/10). I tried updating my import to "Testing log 2", "01:35:51", "Tue, 17/10 10:02:45 – 11∶38∶31","testing:planning:new app", but it just crashes the app.
How the log is exported, the Logs will work if you add a space between the time and day at the first set inside timedate.
The date is using the wrong format. It's failing because it expects a month first, day later. So, switching the dates around works. I don't think this is a problem at export but rather how the program is expecting the dates to be.
At least I think this is what's happening, I don't know Vala. But this does make the logs work.
I'm using Khronos 3.7.0 from Flathub.
When I try exporting a log, it works fine, but if I try to import that same log, it shows the start and finish time as null.
This is the exported log:
My guess is this is due to improperly parsing the date, which in my case is in the Slovenian locale.
I'm also guessing this issue can be resolved by forcing a specific locale for exports, instead of using the system-defined one (
2022-06-25 16:05:42-16:05:48
seems much more readable in exports to me anyway).When imported the result looks like this:
The text was updated successfully, but these errors were encountered: