Bug - Not A Bug svn cannot be accessed

edgy

Member
Ran into an issue where Universal Recovery would always fail because the script couldn't update. While the always failing part is a Universal Recovery issue, svn not working seems to be a global issue. There might also be a case for expanding svn_exists() to actually check if svn can be connected to.

Code:
> ash svn_exists("mafiarecovery")

Returned: true

> svn update mafiarecovery

Validating repo...
svn: E175002: connection refused by the server
Something went wrong while fetching svn directory info
Done.

> svn update eatdrink

Validating repo...
svn: E175002: connection refused by the server
Something went wrong while fetching svn directory info
Done.

Edit: Issue appears in Kolmafia v16.3 r14150. Has not been tested on other revisions.
 
Last edited:

fronobulax

Developer
Staff member
> ash svn_exists("mafiarecovery")

Returned: true

> svn update mafiarecovery

Validating repo...
Repo validated.
Updating mafiarecovery...
C:\KoLMafia\dist\svn\mafiarecovery
At revision 9
Done.
Requests complete.

Cannot reproduce 14152 circa 9:12 Am EST July 4. This is almost certainly a case of SourceForge or the connection thereto being flaky.
 

edgy

Member
Still not working here, but it's most certainly a sourceforge issue. Even trying to load sourceforge.net either takes a long time or it times out.
 
Last edited:

Theraze

Active member
And Universal Recovery (and zlib, and some other scripts) ignoring mafia's settings and forcing an SVN update means that the script author has chosen not to allow you to use their script when the SVN server is down. It's not a 'bug' exactly, but it leads to some unintended consequences like you not being able to use UR, zlib (or anything employing zlib's check_version for SVN) at all when your connection to the SVN is flaky or down. Go talk to the script authors if you want them to change their scripts. Or take it out of your SVN copy and only update when you choose and have things actually work. Your choice. :)
 
Top