Bug? Status of working copy reported as missing when accessed through network share with TortoiseSVN 1.13.1

[Thomas Alias]

After updating from TortoiseSVN 1.12.2 to TortoiseSVN 1.13.1 I experienced a problem that can be reproduced as follows:

1. Checkout a repository path on computer A.
2. Share the new working copy over network (wc-root = share-root).
3. Open the list of shares provided by computer A from computer B.
   
4. From computer B select "Check for modifications" as the context menu option of the share created in step 1.
5. See Status of the root directory of the working copy reported as "missing"

This can also be seen with the command line client provided by TortoiseSVN:

C:\Users\ta>svn status \\computer-a\shared-working-copy

!       \\computer-a\shared-working-copy

This seems to depend on the TortoiseSVN version installed on computer B. With 1.12.2 and earlier the status is reported normal. With 1.13.1 the status of the root directory of the working copy is reported as missing.

This only seems to happen if the working copy is directly shared (wc-root = share-root), not if the working copy lives in a sub directory of the share.

[Johan Corveleyn]

On Wed, Apr 15, 2020 at 9:59 AM Thomas Alias via TortoiseSVN
<tortoisesvn+APn2wQenVkVl8K8pYunE...@googlegroups.com>
wrote:

Perhaps this is related to the same underlying problem as when
accessing a working copy on the root of a subst-ed drive ("subst W:\
C:\Path\to\workincopy"), which was reported here earlier. This problem
has been pinpointed to the underlying APR library that is being used
(TortoiseSVN 13.x switched that library to APR 1.7.0 (previously
1.6.5)). If you take a nightly TSVN build, it should work again,
because it was switched back to APR 1.6.5. So the next TSVN release
should also no longer have this problem.

I've brought that issue to the apr development mailinglist, where it
is under discussion:
https://lists.apache.org/thread.html/r28e478074055436b27b13f7487203448079aea5adfe4207007ad7ea9%40%3Cdev.apr.apache.org%3E

Apparently, the problem was not specific to "subst", but simply to
"working copies on drive roots" (same problem happens when you do a
checkout to the root of a real drive, e.g. C:\).

--
Johan