Hi , Running into the same issue here with TSVN 1.14.1 , unconfirmed from other uses that this is occurring on other versions as well
Behaviour : > Large merges fails with "REPORT request on '/svn/repo/!svn/me' failed" > Diff between commits containing large changesets fails with the same error > No error on the apache error logs > Apache access logs show a series of 207 returns when the error occurs > Issue is reproducible on the windows command line client > Issue NOT reproducible on linux command line client > Apache timeout set to 600 > Have disabled the anti-virus and tested , error still occurs Thanks, Jesse On Thursday, August 12, 2021 at 12:39:43 AM UTC+5:30 Pavel Lyalyakin wrote: > Hello, > > On Tue, Aug 10, 2021 at 11:19 PM Daniel Sahlberg via TortoiseSVN < > [email protected]> wrote: > >> tisdag 10 augusti 2021 kl. 16:07:40 UTC+2 skrev Tina C.: >> >>> Pavel and Daniel: >>> >>> 1. We believe the upgrade is possibly coincidental, but we can try >>> reverting to a previous version. If it IS an issue with the current >>> version, are you aware of or have there been reports of a problem with the >>> new version? Or are you suggesting we revert merely to rule it out? >>> >> >> I agree it might be coincidental, but it is better knowing than believing >> in this case. >> >> >>> 2. Our network connection is stable and unchanged, beyond some TLS >>> updates. This issue is repeatable on different machines using the same >>> software, all trying to push the same revision. >>> >> 3. Our internal network traffic doesn't push through a firewall. >>> 4. I'm not running any antivirus in the background beyond Defender. >>> This seems to be an issue with sheer size of the revision and the fact >>> that it is both deleting files/folders and adding new ones. >>> >> >> Subversion issue 3264 seems to have more or less the same error message. >> >> >> https://issues.apache.org/jira/browse/SVN-3264?jql=project%20%3D%20SVN%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20text%20~%20%22timeout%22 >> > > I doubt that the problem Tina reports and #3264 are related. I still > suggest focusing on troubleshooting the network or any other applications > that could affect the Subversion client's traffic. > > > * As far as I know, modern Subversion clients display a different error > when problem #3264 is involved: > > [[[ > > Error: ra_serf: The server sent a truncated HTTP response body. > > ]]] > > > I want to note that I've just reproduced problem #3264 with TortoiseSVN > 1.14.1 when performing merge (huge directory added). The error is "Error: > ra_serf: The server sent a truncated HTTP response body". > > > * The user says that the error occurs after only a few seconds. However, > in the case of #3264 it should be at least several minutes, not seconds. > > [[[ > > It adds the directory and the first four or five files in the new > directory, then *fails after only a few seconds*. > > ]]] > > >> There are a few things to note about this bug: >> - There are some timeout that can be set in Apache httpd (which is the >> server component behind VisualSVN Server). I'm not sure how to configure >> the timeouts in VisualSVN - Pavel will surely be able to answer. >> - One of the points, (too much time spent on "installing" a working file) >> has been fixed in a recent commit in Subversion. I don't know when that >> commit will hit a release. >> >> Do you see a large CPU and/or disk activity on either the client or on >> the server (check with Resource monitor) during the merge? >> >> If it is caused by timeouts due to the client (or server) being busy >> waiting for the disk, then maybe you can try to put the working copy on a >> faster disk (or maybe even temporarily on a ramdrive)? >> >> The revision reflects un upgrade we implemented on our application. It's >>> upgrading a third-party plugin from an old version to a new version. It's >>> simply deleting out the old folders and files and replacing them with new >>> ones. There are about 100-120 megabytes' worth of files, which doesn't >>> seem significant. >>> >>> The only similar issues I can find online indicate that it happens >>> randomly and only when "a lot" of files are involved in the revision. Some >>> people have managed to get it to work by repeatedly trying. We haven't >>> been so lucky so far. >>> >> >> As I wrote in my initial reply, I believe it might be useful to try to do >> the merge using the command line client instead of the GUI. If you can >> replicate the error also with the command line client, you can send the >> same report to [email protected], where several of the >> Subversion developers are able to answer your questions. >> >> You can readup on the merge syntax in the Subversion book: >> https://svnbook.red-bean.com/nightly/en/svn.branchmerge.html >> >> It should be fairly simple to translate what you have selected in the >> TSVN merge dialog to an SVN commandline. If you don't manage to do it, >> please post a screenshot and we'll see if we can figure it out together. >> >> Kind regards, >> Daniel >> >> >>> >>> -T >>> >>> On Wednesday, August 4, 2021 at 6:42:25 AM UTC-4 Pavel Lyalyakin wrote: >>> >>>> Hello Tina, >>>> >>>> >>>> If you assume that this is a new problem that started only after you >>>> upgraded TortoiseSVN to version 1.14.1, please double-check and confirm >>>> that the problem does not occur with the older version you used before the >>>> upgrade. What version did you use before installing 1.14.1? Were there any >>>> other changes on your side around the time when the problem started? >>>> >>>> >>>> These particular errors in the server's log and the error REPORT >>>> request on '[my-path-to-svn]' failed on the client side could occur due to >>>> network problems. As Daniel already noted, the connection died >>>> unexpectedly. There could be several reasons for this. Please, consider >>>> the >>>> following suggestions: >>>> >>>> >>>> >>>> - Make sure that your network connection is stable. You could try >>>> to use another network to perform the same merge and see if it works. >>>> - Investigate if your traffic passes through an active firewall >>>> with traffic inspection. It is possible that the firewall makes the >>>> connection drop unexpectedly. >>>> - If you use any other antivirus application besides Windows >>>> Defender, investigate if it intercepts your traffic and drops the >>>> connection. It is possible that adding exclusions or tuning the >>>> settings of >>>> your antivirus application will help. >>>> >>>> >>>> As I said, there could be several reasons for this problem. But >>>> usually, troubleshooting of such cases narrows down to network problems, >>>> firewalls, and antivirus applications. >>>> >>>> >>>> Please note that if you encounter any problems when using VisualSVN >>>> Server, you could contact [email protected] for technical >>>> assistance. >>>> >>>> >>>> Hope this information helps! >>>> >>>> On Mon, Aug 2, 2021 at 4:45 PM Tina C. via TortoiseSVN wrote: >>>> >>>>> Hi Daniel: >>>>> >>>>> The Event Log on the Windows server generates three "warnings" under >>>>> the VisualSVN Server: >>>>> >>>>> *Warning #1:* * "Provider encountered an error while streaming a >>>>> REPORT response. [500, #0]"* >>>>> *Warning #2: "**A failure occurred while driving the update report >>>>> editor [500, #730054]"* >>>>> *Warning #3: "The connection was closed by the remote host [500, >>>>> #730054]"* >>>>> >>>>> I hope that helps. >>>>> >>>>> -T >>>>> >>>>> >>>>> >>>>>> Can you access the error log on the server to see if it provides some >>>>>> information? >>>>>> >>>>>> I *think* I can see where in the code this happens, but the comment >>>>>> is: /* Uh-oh. Our connection died. */ >>>>>> >>>>>> Kind regards, >>>>>> Daniel >>>>>> >>>>> -- >>>>> >>>> You received this message because you are subscribed to the Google >>>>> Groups "TortoiseSVN" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/tortoisesvn/7e817eac-995e-4a21-ba9d-8ed7b56ad068n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/tortoisesvn/7e817eac-995e-4a21-ba9d-8ed7b56ad068n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> >>>> -- >>>> With best regards, >>>> Pavel Lyalyakin >>>> VisualSVN Team >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "TortoiseSVN" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/tortoisesvn/478e56b6-c228-4332-9cc0-3e7f25b88d40n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tortoisesvn/478e56b6-c228-4332-9cc0-3e7f25b88d40n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c10782e4-7578-4a94-af2c-43e4ee4f9cc5n%40googlegroups.com.
