RE: svn commit: r1651980 - in /subversion/trunk/subversion: libsvn_wc/wc_db.c tests/libsvn_wc/op-depth-test.c
From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 15 Jan 2015 11:07:31 +0100
> -----Original Message-----
This is a common pattern in the move handling, which really isn't stable yet (especially during updates). We like the information about these missed matches during testing, but the move lookup code verifies whether there is a match ing src and destination before handling a node as moved.
Eventually somebody would have reported that he moved a file, but didn't see it as a move in status (or see it handled as move during update). Yes, that delays the report, but as long as we don't have server side move handling nothing really breaks when move information gets lost.
The 'assert(SOMETHING);' statements in the code are assumed to be left out in release builds, while SVN_ERR_ASSERT() statements are assumed to be left in.
SVN_ERR_ASSERT() can either abort() or return an error depending on what the api user wants to happen.
The problem here is that this specific user got an assert() triggering, so I switched it to the same code as at least 3 or 4 other functions have for similar cases.
This is an archived mail posted to the Subversion Dev mailing list.