Open GoogleCodeExporter opened 9 years ago
This is most certainly a bug. There is a mutex that is held while the session
is being modified, but the problem is that the session is not locked until the
actual commit starts. The list of files to commit are gathered before that
happens, making your scenario possible. This will need fixing.
Original comment by ekb...@gmail.com
on 17 Feb 2014 at 8:24
I have pushed a temporary fix in changeset 094ecd048538 that aborts the
long-running commit if there has been any intervening commits. Not too bad user
experience, the scan has already been completed and you just need to do an
update and then try again.
Final solution will probably be to lock the session for the duration of the
commit.
Original comment by ekb...@gmail.com
on 17 Feb 2014 at 8:42
Original issue reported on code.google.com by
david.ch...@gmail.com
on 17 Feb 2014 at 7:17