-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No active tracking after start #605
Comments
@dakotak I see there is a Can you try to manually create a |
@lauft I can see the files in ~ → ll ~/.data/timewarrior/data
.rw-r--r-- dakota staff 106 B Wed May 8 19:48:11 2024 2024-05.data
.rw-r--r-- dakota staff 47 B Wed May 8 19:48:11 2024 tags.data
.rw-r--r-- dakota staff 361 B Wed May 8 19:48:11 2024 undo.data
~ → timew start test2
Note: 'test2' is a new tag.
Tracking test2
Started 2024-05-08T19:50:05
Current 05
Total 0:00:00
~ → timew
There is no active time tracking.
~ → ll ~/.data/timewarrior/data
.rw-r--r-- dakota staff 135 B Wed May 8 19:50:05 2024 2024-05.data
.rw-r--r-- dakota staff 70 B Wed May 8 19:50:05 2024 tags.data
.rw-r--r-- dakota staff 456 B Wed May 8 19:50:05 2024 undo.data
~ → mkdir ~/.timewarrior
~ → timew
There is no active time tracking.
~ → timew start test2
Note: 'test2' is a new tag.
Tracking test2
Started 2024-05-08T19:50:55
Current 55
Total 0:00:00
~ → timew
Tracking test2
Started 2024-05-08T19:50:55
Current 51:00
Total 0:00:05
~ → ll ~/.timewarrior/data
.rw-r--r-- dakota staff 29 B Wed May 8 19:50:55 2024 2024-05.data
.rw-r--r-- dakota staff 25 B Wed May 8 19:50:55 2024 tags.data
.rw-r--r-- dakota staff 95 B Wed May 8 19:50:55 2024 undo.data |
@dakotak Debugging further... When using XDG, how does the output of |
@lauft Here are the outputs from running ~ → timew start test2 :debug
CLI Parser
_original_args
timew start test2 :debug
_args
word basename='timew' raw='timew' BINARY
word canonical='start' raw='start' ORIGINAL CMD
word raw='test2' ORIGINAL FILTER TAG
word canonical=':debug' raw=':debug' ORIGINAL HINT FILTER
>> 2024-05.data: 2 intervals
>> Loaded 0 tracked intervals
>> 2024-05.data: Added inc 20240511T122146Z # test2
Tracking test2
Started 2024-05-11T05:21:46
Current 46
Total 0:00:00
>> Moving '/Users/dakota/.timewarrior/data/2024-05.data.70516-2.tmp' -> '/Users/dakota/.timewarrior/data/2024-05.data'
>> Moving '/Users/dakota/.timewarrior/data/undo.data.70516-3.tmp' -> '/Users/dakota/.timewarrior/data/undo.data'
>> Moving '/Users/dakota/.timewarrior/data/tags.data.70516-4.tmp' -> '/Users/dakota/.timewarrior/data/tags.data'
>> Timer timew 0.023992 sec And after removing ~ → rm -rf ~/.timewarrior
~ → timew start test
Tracking test
Started 2024-05-11T05:22:24
Current 24
Total 0:00:00
~ → timew
There is no active time tracking.
~ → timew start test2 :debug
CLI Parser
_original_args
timew start test2 :debug
_args
word basename='timew' raw='timew' BINARY
word canonical='start' raw='start' ORIGINAL CMD
word raw='test2' ORIGINAL FILTER TAG
word canonical=':debug' raw=':debug' ORIGINAL HINT FILTER
>> Loaded 0 tracked intervals
>> 2024-05.data: 6 intervals
>> 2024-05.data: Added inc 20240511T122239Z # test2
Tracking test2
Started 2024-05-11T05:22:39
Current 39
Total 0:00:00
>> Moving '/Users/dakota/.data/timewarrior/data/2024-05.data.71170-2.tmp' -> '/Users/dakota/.data/timewarrior/data/2024-05.data'
>> Moving '/Users/dakota/.data/timewarrior/data/undo.data.71170-3.tmp' -> '/Users/dakota/.data/timewarrior/data/undo.data'
>> Moving '/Users/dakota/.data/timewarrior/data/tags.data.71170-4.tmp' -> '/Users/dakota/.data/timewarrior/data/tags.data'
>> Timer timew 0.022123 sec
~ → timew
There is no active time tracking. |
After starting tracking it seem that time warrior does not find any entries. Issue seems similar to #146 but seems different as the database file name is correct.
I removed the database files and config files with the same result.
Diagnostics:
I have been using time warrior on my work computer (also osx) without any issues, but after installing on my personal computer I have not been able to get it to work.
14.3.1
The text was updated successfully, but these errors were encountered: