Project Monitor: Update All doesn't update to latest version!

[Justin MASSIOT | Zentek]

Hello everyone,

I've recently installed the Project Monitor (TortoiseSVN 1.14.5) to be notified of modifications on some repos I work on. But I noticed what I suppose to be a bug...

Context:

My Project Monitor currently tracks 2 Working Copies:

1) AltiumDesigner_AddOns in C:\AltiumDesigner_AddOns

2) AltiumDesigner_ContentCentral in C:\AltiumDesigner_ContentCentral

Both are up-to-date, HEAD revisions are 728 and 1727, respectively.

What happens:

Project Monitor being aware WCs are up-to-date, I click the "Update All" button.

1) AltiumDesigner_AddOns updates correctly (no change in the WC)

2) AltiumDesigner_ContentCentral updates and brings many modifications to my WC, saying at the end: "Completed    At revision: 728" (instead of 1717)

So the HEAD revision of the first repo is used to update both repositories!!

What I expected:

The expected behavior here is to update all repositories to HEAD, am I right? :-)

Workaround:

"Update All" works as expected if I have only one repo listed in the Project Monitor.

Could this bug be addressed in a future release?

Thank you!

Justin MASSIOT  |  Zentek

[Daniel Sahlberg]

fredag 22 september 2023 kl. 09:41:26 UTC+2 skrev Justin MASSIOT:

Hello everyone,

I've recently installed the Project Monitor (TortoiseSVN 1.14.5) to be notified of modifications on some repos I work on. But I noticed what I suppose to be a bug...

Context:

My Project Monitor currently tracks 2 Working Copies:

1) AltiumDesigner_AddOns in C:\AltiumDesigner_AddOns

2) AltiumDesigner_ContentCentral in C:\AltiumDesigner_ContentCentral

Both are up-to-date, HEAD revisions are 728 and 1727, respectively.

What happens:

Project Monitor being aware WCs are up-to-date, I click the "Update All" button.

1) AltiumDesigner_AddOns updates correctly (no change in the WC)

2) AltiumDesigner_ContentCentral updates and brings many modifications to my WC, saying at the end: "Completed    At revision: 728" (instead of 1717)

So the HEAD revision of the first repo is used to update both repositories!!

What I expected:

The expected behavior here is to update all repositories to HEAD, am I right? :-)

Agree with your expectations.

 

Workaround:

"Update All" works as expected if I have only one repo listed in the Project Monitor.

Could this bug be addressed in a future release?

I tried to reproduce it (adding four different WCs from my computer) but all were updated to the correct HEAD revision, I'm getting "Completed At revision: 311" followed by revisions 490, 1560, 28 (all numbers seem correct).

Kind regards,

Daniel

[Stefan]

when updating multiple paths, TSVN tries to update all of them to the same revision, because there's a possible race condition when just updating to HEAD.

Of course, TSVN only does that if all the paths to be updated are from the same repository. And that is checked by comparing the repository uuid.

So, in your case it seems that both repositories have the same uuid - which can cause many problems, not just the one you're describing here. I mean it's called an UUID for a reason: it MUST be unique.

use the 'svnadmin setuuid' command on one of the repos to change the uuid to something else, then do a fresh checkout.

[Justin MASSIOT]

Well caught Stefan, my two repositories indeed have the same UUID. Which I wasn't aware of until now!

I suppose one repo is a copy of the other because they shared the same root some while ago.

As you suggested, I've set a new UUID and have done a fresh checkout. Then the Project Monitor works OK if I click Update All.

Problem solved, thanks for your support!

Justin