subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Martin <philip.mar...@wandisco.com>
Subject Re: E235000: assertion failed (SVN_IS_VALID_REVNUM(new_revision))
Date Wed, 21 Jan 2015 13:16:54 GMT
Tomasz Grobelny <tomasz.grobelny@makingwaves.pl> writes:

>> That's failed in the code that runs on the client after the commit
>> has succeeded.  It appears that the the client is acting as if the
>> commit worked on the server but it has not got the newly committed
>> revision.  If you look at the server/repository did the commit
>> succeed?
>> 
> No it didn't - I cannot see the changes on the server (now connecting
> to it as TFS repo).

The client sends an HTTP MERGE request to make a commit.  When the
commit is successful the server sends a 200 OK response that includes
the new revision number and the client updates the working copy.  In
your case it seems the server sent a response that the client
interpreted as a successful commit but without the new revision number.
We would really like to see a network trace of the response.

The client may have broken the working copy when it tried to apply the
missing revision number.  You may have to check out a second working
copy, compare to the first and manually transfer the changes to the
second working copy.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*

Mime
View raw message