-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
task sync
doesn't update the sync.server.client_id
value
#3613
Comments
Wondering if this could be related to #3611? |
Some messing around with the config finally caused both computers to request with |
Could there be some strange behaviour when including files? I initially set everything up using |
I would guess that this is not the case, when I remove the Is there some caching of the |
Also, |
This shouldn't be possible, as the value is read from It's read from taskwarrior/src/commands/CmdSync.cpp Line 72 in 2e3badb
and passed to TaskChampion here: taskwarrior/src/commands/CmdSync.cpp Lines 103 to 104 in 2e3badb
And you can see in the TaskChampion source that there's no "get_cached_client_id" or anything of the sort in the storage API. |
Also, did you provide an all-zeroes client_id at some point? It really shouldn't be defaulting to that.. |
I never provided an all-zeros client_id, no... But it did change later back to the originally set value. The main issue seems to be the
|
OK, I'm pretty confused now! If this is working for you, great -- I'm happy to leave it. But if not, can you reduce it to one problem and one change that reproduces it? I'm not sure if we're talking about |
The closest I can get to reproduce it would be this, though with valid encryption secrets, client UUIDs and server urls:
I initially thought something like read / write access to the file was the problem, or the fact it was symlinked, but it seems to occur even when I create a new file, as above. Could |
Ok now this is strange, I compiled taskwarrior myself, and added print statements to the CmdSync.cpp file, and while it prints the correct client id, the client id which is actually logged to the server is the wrong one... So it seems like the issue is somewhere between the |
Is there a way to enable / get logs from the taskchampion crate? |
Ah, I see the issue -- the client ID does not appear in the URL. See https://gothenburgbitfactory.org/taskchampion/http.html#getchildversion. What you're reading as the client ID is, in fact, the parent version ID. For initial synchronization, that will be the nil UUID (all zeroes).
TC uses the |
Ah ok, so does that mean that the id in the url is irrelevant to what the client id, as set in the taskrc, is? I'll run the same test as I outlined above again, but try to add and complete some tasks in between, to test if everything syncs correctly. |
Yep, totally unrelated |
@martiege what did you figure out? |
I recently set up a taskchampion sync server, and wanted to test it out with two of my computers. Initially I set it up with two separate uuids, but when I realised this was not what I wanted to do, I changed the
sync.server.client_id
field to be the same for both computers.Inspecting the log of my taskchampion sync server instance, I see that the actual GET calls I receive when I run
task sync
on the two different instances are the old uuids I initially generated, rather than the new one I generated to be common for both my computers.Expected behaviour:
Setting the
sync.server.client_id
field withtask config sync.server.client_id ****
will change the client id used bytask sync
.Current behaviour:
The first, valid,
client_id
set is used and never updated.Output of
task diag
:The text was updated successfully, but these errors were encountered: