# Getting latest changesets dies on changes where the comments contains backslashes and questions marks

**URL:** https://www.finalbuilder.com/forums/t/getting-latest-changesets-dies-on-changes-where-the-comments-contains-backslashes-and-questions-marks/6075
**Category:** Bugs
**Created:** [January 11, 2017, 6:58am UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-dies-on-changes-where-the-comments-contains-backslashes-and-questions-marks/6075 "2017-01-11T06:58:17Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![miruna](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/m/f17d59/32.png) [@miruna](https://www.finalbuilder.com/forums/u/miruna)
#### Post date: [January 11, 2017, 6:58am UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-dies-on-changes-where-the-comments-contains-backslashes-and-questions-marks/6075/1 "2017-01-11T06:58:17Z")

</div>

Continua 1.8.0.243. I have a Subversion repository that stopped getting latest. I’m attaching the full error message.   
  
It looks like hg.exe choked on a commit comment that contained “” and “??”. I’m not sure which one causes it, but editing the comment to take both out got the repository to update again.   
  
hg.exe version in C:\Program Files\VSoft Technologies\ContinuaCI\Server\hg is 3.5.0.0  
  
  
[\_\_39109\_\_0\_\_Message.zip](https://www.finalbuilder.com/forums/uploads/default/original/2X/a/a2c9818094dd7d731a1c55fb7db43d80189aca98.zip) (1.235 KB)

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [January 12, 2017, 3:21am UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-dies-on-changes-where-the-comments-contains-backslashes-and-questions-marks/6075/2 "2017-01-12T03:21:36Z")

</div>

Hi Miruna,  
  
Thank you for reporting this. We have now reproduced an implemented a fix for an issue with escaping the " combination. The fix will be in the next version.
