Log Messages are not generated in Repo-browser

[Peter Ferndriger]

In Repo-browser the Log Messages are missing. In the checkouts it's working fine.

This error is since TortpoiseSVN 1.10.1. 

Actual there is installed version 1.10.2, Build 28392 - 64 Bit

[peter.fe...@hispeed.ch]

There is an error " File not found: revision 883, path '/onitoringSystem' ", when the Log Messages is called in the Repo-browser on
"file:///Q:/.../code/svnRepos/JCMonitoringSystem"

This bug exists since TortoiseSVN 1.10.1.
Actual there is installed TortoiseSVN 1.10.2, Build 28392 - 64Bit

Log Messages are correctly generated on Checkouts.

[se...@gambierrip.ca]

I was just getting set to report this bug myself. Here are a few more details:

- The problem is that the first character of the path is being stripped from the log request URL. Notice in Peter's first screenshot that the path is '/onitoringSystem' instead of '/MonitoringSystem'.

- In my testing I found that the problem occurs when the repository name contains spaces. An otherwise identical repository without spaces allows log viewing in repo-browser.

- using the command line svn application to view logs works fine (only present when viewing logs from Tortoisesvn repo-browser).

- The error occurs with svn:// URLs as well as file:// URLS (I did all my testing with svn://)

- Turning on logging in svnserve appears to show that the request coming from tortoise SVN has the malformed URL, so it appears to not be server related.

- The problem is not present in TortoiseSVN 1.9.7, but is in 1.10.1 & 1.10.2 (I did not test 1.10.0)

[se...@gambierrip.ca]

Replication for my testing:

1) Create a repository called "RepoTesting".
2) Check out the repository, commit a folder "SomeDir" with a file in it ("SomeFile.txt")
3) Modify the contents of SomeFile.txt and commit. We now have some a couple of revisions to see in the log.
4) Create a repository called "Repo Testing" and repeat steps 2 & 3 for it.
5) use right-click > TortoiseSVN > Show Log on the checkout of "Repo Testing/SomeDir". It should work fine.
6) use right-click > TortoiseSVN > Show Log on the checkout of "Repo Testing/SomeDir". It should work fine.
7) use the Repo-browser, open "svn://servername/RepoTesting", right-click on SomeDir and show log. It should work fine.
8) use the Repo-browser, open "svn://servername/Repo Testing", right-click on SomeDir and show log. It will FAIL with the error "File not found: revision #, path '/omeDir'". Notice the path is /omeDir not /SomeDir.


One final detail I forgot to add, even with a repository name containing spaces, doing a Show Log on the root of the repository *does* work. My conjecture is that this is because stripping a char from an empty path is still empty.

[Stefan]

Ok, first:

Do not use the file:/// protocol over network shares!

Second:

Do not use the file:/// protocol over network shares!

https://tortoisesvn.net/faq.html#reponoserver

Also, you should not have spaces in the url leading to the repository or the repository itself. You can have as many spaces and special chars inside a repository url, but not leading up to it. You'll only get into trouble.

And last:

I've fixed this special case in r28404.

And just in case you think that the warning about corrupted repositories that are accessed via file:/// on a network share doesn't apply to you: I had a user lose 5 years of data just four months ago - the backup was corrupted too because they didn't notice the problem soon enough.

So please: make a backup of your repository NOW. Then use the command line client to dump the repository, then create a new one and try to import that dump. If you get any errors while dumping or importing the dump then you're screwed. If not, then you have a little time to set up a real server. So do that now, don't wait until tomorrow.

Stefan

[Peter Ferndriger]

Thanks a lot for your answers.

So the first step will be to avoide space chars in the path, especially in the leading part of the url.

Secondly: reorganizing the repos in accordance with the mentioned link (https://tortoisesvn.net/faq.html#reponoserver)

By the way, in version 1.10.0 the url with spaces was still working fine. 

Peter

[se...@gambierrip.ca]

On Wednesday, October 17, 2018 at 11:18:02 AM UTC-7, Stefan wrote:

> And last:
> I've fixed this special case in r28404.
>

I can confirm that using the nightly "1.10.2, Build 28405 - 64bit -dev" I can now view logs both on my test repositories and our production repositories from the repo-browser (both via svn:// urls).

Thanks!