svnpubsub/client.py: RuntimeError: dictionary changed size during iteration

2018-08-23 Thread sebb
When running a version of watcher.py I got the following error:

  File ".../svnpubsub/client.py", line 251, in run_forever
self._check_stale()
  File ".../svnpubsub/client.py", line 216, in _check_stale
for client in asyncore.socket_map.values():
RuntimeError: dictionary changed size during iteration

Is this a known issue?

S.


svnserve 'marshal.c' line 920: assertion failed (SVN_IS_VALID_REVNUM(rev))

2018-08-23 Thread Ace Olszowka
 Hi

The TortoiseSVN Mailing List asked that I post this to the Subversion Users
Mailing list

TortoiseSVN 1.10.0.28176 (64 bit) / Windows Server 2016 1607

We have been using svnserve.exe to host up a pretty large subversion
repository (~170,000 Revisions, ~150 Users).

We just encountered a Unhanded Exception and were able to capture a dump
via ProcDump [procdump /i /ma] in fact two dumps were captured. About 2
seconds after each other, the stack traces appear to be identical.

Error:
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.10.0\ext\subversion\subversion\libsvn_ra_svn\marshal.c'
line 920: assertion failed (SVN_IS_VALID_REVNUM(rev))

Stack Trace:
 ucrtbase.dll!abort ()Unknown
>libsvn_tsvn.dll!svn_error_abort_on_malfunction(int can_return, const
char * file, int line, const char * expr) Line 849C
 [Inline Frame] svnserve.exe!vwrite_tuple_revision(svn_ra_svn_conn_st
*) Line 920C
 svnserve.exe!vwrite_tuple(svn_ra_svn_conn_st * conn, apr_pool_t *
pool, const char * fmt, char * * ap) Line 1182C
 svnserve.exe!svn_ra_svn__write_cmd_response(svn_ra_svn_conn_st * conn,
apr_pool_t * pool, const char * fmt, ...) Line 2758C
 svnserve.exe!get_deleted_rev(svn_ra_svn_conn_st * conn, apr_pool_t *
pool, svn_ra_svn__list_t * params, void * baton) Line 3510C
 svnserve.exe!svn_ra_svn__handle_command(int * terminate, apr_hash_t *
cmd_hash, void * baton, svn_ra_svn_conn_st * conn, int error_on_disconnect,
apr_pool_t * pool) Line 1946C
 svnserve.exe!serve_interruptable(int * terminate_p, connection_t *
connection, int(*)(connection_t *) is_busy, apr_pool_t * pool) Line 4396
C
 svnserve.exe!serve_thread(apr_thread_t * tid, void * data) Line 639
C
 libaprutil_tsvn.dll!thread_pool_func(apr_thread_t * t, void * param)
Line 267C
 [External Code]


Unfortunately the dump looks like its got a lot of private information in
here, I am willing to help as much as possible but cannot share the dump
publicly.

I've already grabbed the PDB's (From
http://www.drdump.com:8080/public/tsvn/71040F62-F78A-4953-B5B3-5C148349FED7/symsrv)
and the Source (From
https://svn.apache.org/repos/asf/subversion/branches/1.10.x/subversion/)

Near as I can tell from my groveling it appears one of our CI Servers
attempted to grab a log (probably to determine if it should build or not)
when this error occurred. To spice it up a bit we were right in the middle
of updating the authz file which was updated incorrectly. The rev variable
from vwrite_tuple_revision is gone ("Variable is optimized away and not
available").

Digging into get_deleted_rev some of the information looks "valid" in the
sense that I don't see any corruption; full_path looks to be a folder
within the repository, however this folder was deleted a few days ago
(2018/08/17 under revision 164376) and peg_revision is valid (164369) its
interesting to note that that revision is lower than the one that contains
the deletion of the folder.

I'm willing to work to try and track down the issue if someone could give a
few pointers, I can share information out of the dumps (removing any
private information along the way).

Searching online I don't think anyone else has encountered this error (at
least that I have been able to see) it looks like we're 1 release back on
TortoiseSVN however, and we're willing to upgrade.

We did encounter an unhandled exception which crashed the svnserve services
a few weeks ago, but at the time didn't have procdump setup (which is why
it was setup now).


Error report: wc_db.c line 1648: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))

2018-08-23 Thread Christoph Hannebauer
Hi,

 

I have not subscribed to the users mailing list, so please CC me in this
thread.

 

My SVN crashed with this error message:

'D:\Development\SVN\Releases\TortoiseSVN-1.10.1\ext\subversion\subversion\li
bsvn_wc\wc_db.c'

line 1648: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))

 

What I did before the crash, was execute the following command:

svn checkout
https://github.com/Microsoft/Windows-classic-samples/trunk/Samples/Win7Sampl
es/security/certificateservices/exit/c++/WindowsServer2008R2

 

I didn't check whether other machines also show this behavior, but I did
check that TortoiseSVN 1.9.7 is also affected.

 

 

Best,

 

Christoph



smime.p7s
Description: S/MIME cryptographic signature


Re: Error report: wc_db.c line 1648: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))

2018-08-23 Thread Nathan Hartman
On Thu, Aug 23, 2018 at 9:46 AM Christoph Hannebauer <
christoph.hanneba...@glueckkanja.com> wrote:

> I have not subscribed to the users mailing list, so please CC me in this
> thread.
>
>
>
> My SVN crashed with this error message:
>
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.10.1\ext\subversion\subversion\libsvn_wc\wc_db.c'
>
> line 1648: assertion failed (SVN_IS_VALID_REVNUM(changed_rev))
>
>
>
> What I did before the crash, was execute the following command:
>
> svn checkout
> https://github.com/Microsoft/Windows-classic-samples/trunk/Samples/Win7Samples/security/certificateservices/exit/c++/WindowsServer2008R2
>
>
>
> I didn’t check whether other machines also show this behavior, but I did
> check that TortoiseSVN 1.9.7 is also affected.
>
>
>
>
Interesting. There is another thread about an assertion failure, also in a
call to SVN_IS_VALID_REVNUM(), but in a different file. Could these be
related?



>