Re: Error E170013: The server unexpectedly closed the,connection.
Hi, According to the user this error occurs now permanently on macOS 10.15 for him while in previous versions it only occurred sometimes with macOS 10.14/15, but not with 10.12/13. -- Best regards, Thomas Singer On 2020-11-26 8:41, Thomas Singer wrote: Hi, A user of SmartSVN with SVN 1.14 reports a problem in connecting to the SVN server while it works in the browser. I redirected him to use our self-built SVN 1.14 binaries and he reports following error MacBook-Pro:user$ svn update Updating '.': *svn: E170013*: Unable to connect to a repository at URL ' https://svn.workapps.com/svn/OneWorkbook/trunk' *svn: E120108*: Error running context: The server unexpectedly closed the connection. How to diagnose the problem? Is it a problem of SVN or the server? Thanks in advance.
Re: Source Code Build Errors?
As far as a Windows build, I have this script that works. Might help as a starting point. Has some weirdness with tests. Stops on 60/121 that I need to investigate. But a previous version of the script ran all tests. I think it might be because of Python 2.7 because I used 3.8 when I remember it working last. https://gist.github.com/ahwm/47dca1ae4290094a539d5dcc30338fb9 From: Alan Fry Sent: Thursday, November 26, 2020 17:47 To: Branko Čibej Cc: Subversion Developers Subject: Re: Source Code Build Errors? Excellent, thank you. So the target is "all tests succeeded". And thank you, I'll dive into the tests.log file. I'm sure the errors are due to the build that I'm trying, not actual faults in the code. On Tue, Nov 24, 2020 at 1:45 PM Branko Čibej mailto:br...@apache.org>> wrote: On 24.11.2020 19:05, Alan Fry wrote: > Having some time finally to work on building SVN (thanks all who > helped me get this far), I setup a VM with Ubuntu. (Also setup a > Windows 10 machine w/ Visual studio, but have not started on that > effort yet). > > Knowing little about linux, I managed to get this far, the results of > make checks > > Last part of the make check: > > At least one test FAILED, checking > /home/svn/Documents/subversion-1.14.0/tests.log > FAIL: error-test 3: test svn_error_symbolic_name > FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained > FAIL: commit_tests.py 48: set revision props during remote property edit > FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) > FAIL: prop_tests.py 16: property operations on a URL > FAIL: update_tests.py 38: update --accept automatic conflict resolution > Summary of test results: > 2508 tests PASSED > 162 tests SKIPPED > 81 tests XFAILED (17 WORK-IN-PROGRESS) > 6 tests FAILED > Python version: 3.8.5. > SUMMARY: Some tests failed > > Are these errors something I need to dig into, indicating that my > build is no good? I was reading in the "INSTALL" document, there is > mention that some errors are expected. Is there a way to determine if > these are expected errors? Expected test failures are tagged as XFAIL, not FAIL. So these are "real" failures. Also the summary line would read "All tests succeeded" if there were only expected failures. You should look at tests.log (the test driver hepfully prints the whole path) to see why those tests failed, it could be something trivial. It's not likely that there's a problem with the code, we'd have noticed that. -- Brane
Re: svn.haxx.se is going away
On Thu, Nov 26, 2020 at 4:16 PM Daniel Sahlberg wrote: > > Den ons 25 nov. 2020 kl 16:40 skrev Greg Stein : > >> On Wed, Nov 25, 2020 at 8:52 AM Daniel Sahlberg < >> daniel.l.sahlb...@gmail.com> wrote: >> >... >> >>> As for the question in your other mail (the reply to Daniel Shahaf) >>> regarding the desire to keep the URLs. My initial question to Daniel >>> Stenberg was if they would consider CNAME:ing svn.haxx.se to my server >>> and he seemed ok with that, however we have not reached a formal agreement. >>> I assume it would be even easier for him to CNAME it to a server provided >>> by the ASF. >>> >> >> I would suggest a CNAME to svn-haxx.apache.org, which Infra would >> further CNAME to (say) svn-qavm. That would mean Mr Stenberg wouldn't ever >> need to alter his CNAME record, while the ASF could repoint svn-haxx.a.o >> at-will over time. Today, the "301 mapping server" could be svn-qavm, but >> maybe we'd do something different in a few years >> > > Now that we seem to have an agreement with Daniel Stenberg, what is the > next step? You mentioned something about volunteer time, so what can we do? > > Do you want to have a 301 redirect from the old urls to another archive, > or is it acceptable to just keep the site as it is? The site is mostly HTML > files with some SSIs. In addition there are a few CGI scripts (perl-based) > but I think these can be replaced with static HTML pages. So if we can keep > the site as it is, then it is is "just" a matter of providing a VHOST where > the site can be uploaded. > I think the first steps should be getting the site as-is uploaded to whatever location Greg indicates and coordinating the CNAME setup with Daniel Stenberg. This will ensure the archive to date remains accessible. Then we can discuss what steps to take next, what form the archive should take, etc. Cheers, Nathan
Re: Source Code Build Errors?
Excellent, thank you. So the target is "all tests succeeded". And thank you, I'll dive into the tests.log file. I'm sure the errors are due to the build that I'm trying, not actual faults in the code. On Tue, Nov 24, 2020 at 1:45 PM Branko Čibej wrote: > On 24.11.2020 19:05, Alan Fry wrote: > > Having some time finally to work on building SVN (thanks all who > > helped me get this far), I setup a VM with Ubuntu. (Also setup a > > Windows 10 machine w/ Visual studio, but have not started on that > > effort yet). > > > > Knowing little about linux, I managed to get this far, the results of > > make checks > > > > Last part of the make check: > > > > At least one test FAILED, checking > > /home/svn/Documents/subversion-1.14.0/tests.log > > FAIL: error-test 3: test svn_error_symbolic_name > > FAIL: locks-test 14: lock/unlock when 'write-lock' couldn't be obtained > > FAIL: commit_tests.py 48: set revision props during remote property edit > > FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel, pe) > > FAIL: prop_tests.py 16: property operations on a URL > > FAIL: update_tests.py 38: update --accept automatic conflict resolution > > Summary of test results: > > 2508 tests PASSED > > 162 tests SKIPPED > > 81 tests XFAILED (17 WORK-IN-PROGRESS) > > 6 tests FAILED > > Python version: 3.8.5. > > SUMMARY: Some tests failed > > > > Are these errors something I need to dig into, indicating that my > > build is no good? I was reading in the "INSTALL" document, there is > > mention that some errors are expected. Is there a way to determine if > > these are expected errors? > > Expected test failures are tagged as XFAIL, not FAIL. So these are > "real" failures. Also the summary line would read "All tests succeeded" > if there were only expected failures. > > You should look at tests.log (the test driver hepfully prints the whole > path) to see why those tests failed, it could be something trivial. It's > not likely that there's a problem with the code, we'd have noticed that. > > -- Brane >
Re: svn.haxx.se is going away
Den ons 25 nov. 2020 kl 16:40 skrev Greg Stein : > On Wed, Nov 25, 2020 at 8:52 AM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >... > >> As for the question in your other mail (the reply to Daniel Shahaf) >> regarding the desire to keep the URLs. My initial question to Daniel >> Stenberg was if they would consider CNAME:ing svn.haxx.se to my server >> and he seemed ok with that, however we have not reached a formal agreement. >> I assume it would be even easier for him to CNAME it to a server provided >> by the ASF. >> > > I would suggest a CNAME to svn-haxx.apache.org, which Infra would further > CNAME to (say) svn-qavm. That would mean Mr Stenberg wouldn't ever need to > alter his CNAME record, while the ASF could repoint svn-haxx.a.o at-will > over time. Today, the "301 mapping server" could be svn-qavm, but maybe > we'd do something different in a few years > Now that we seem to have an agreement with Daniel Stenberg, what is the next step? You mentioned something about volunteer time, so what can we do? Do you want to have a 301 redirect from the old urls to another archive, or is it acceptable to just keep the site as it is? The site is mostly HTML files with some SSIs. In addition there are a few CGI scripts (perl-based) but I think these can be replaced with static HTML pages. So if we can keep the site as it is, then it is is "just" a matter of providing a VHOST where the site can be uploaded. Kind regards, Daniel Sahlberg
