Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,245
Community Members
 
Community Events
168
Community Groups

"Crucible cannot anchor the patch to this repository" with (Tortoise) SVN pre-commits

We routinely see the "Crucible cannot anchor the patch to this repository" error when doing pre-commit reviews.  Details below:

FishEye/Crucible 3.8.1 (also in 3.0.3, the version we're upgrading from)

TortoiseSVN 1.8.11 64 bit (the current version)

Subversion 1.8.13

  1. Edit one of the first few (3 ???) lines of a file
  2. From the Tortoise commit dialog, Create Patch / Save to Clipboard
  3. Paste to pre-commit window in Crucible and upload

Note that the process seems to work fine normally, but fails whenever one or more of the files in the commit has  a change in the first ~3 lines.  A screen shot of the error is shown below.

Is there a fix or workaround for this?

Thanks, Eric

 

Untitled.png

 

2 answers

1 accepted

0 votes
Answer accepted

This was fixed in the GA version of Tortoise SVN as part of version 1.9.0.26652, released August 5, 2015.  We've tested that release in-house and confirmed that it resolves the issue.

I now believe the bug is in Tortoise SVN.  TSVN's "Save to Clipboard" feature is including the start-of-file byte order marker (BOM) in the patch text it's creating.  Pasting the same patch text from the clipboard into Notepad will result in a patch file that breaks TSVN as well.  I've raised the issue on the TSVN mailing list.

Workaround will be to use TSVN's Save to File feature instead, until the issue is fixed in that tool.

lpater Atlassian Team Jul 23, 2015

Please also consider raising an issue at https://jira.atlassian.com/browse/CRUC. We should be able to easily discard the BOM and still parse the patch correctly. Thanks!

Thanks Lukasz. Actually, the issue is already fixed in the nightly TSVN builds, and I expect that fix will go GA any day now. As I understand it, it came down to trying to pass the BOM through the lossy CF_TEXT format when a unicode format was more appropriate. See http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3127411 for more background.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events