Mac OS 10.13.3 Clone Repo get "illegal byte sequence"

[RomeoQNgo]

Hi,

I'm trying to clone a repo on Mac OS 10.13.3 (HG 4.5.2) and I'm getting error "illegal byte sequence" on one of the file when it try to "hg update" to latest commit.  The issue is with file name contain a special character.

 I tried this on Mac OS 10.12.4 with HG 4.5.2 and I don't get this issue at all.

Had anyone have this issue before?  What is your fix beside renaming the file in the repo.

Thanks,

[Ana Retamal]

Hi Romeo! What tool are you using to clone this repo into your computer? This seems to be an issue with Mac, rather than an issue on Atlassian's side. Please give us more information so we can help you troubleshoot this issue :)

Cheers,

Ana

[RomeoQNgo]

Hi Ana,

I use the terminal to clone the repo.  Repo is successfully clone without update.

After a bit more debugging, I found the issue is with hg update where the file name contains special characters.  Below is the log where the error occurs.

I bold and underline the line in the log that has this issue.

I tried all kind of LANG=C, LC_TYPE=C, LC_ALL=C before the hg update command and getting the same error.

~~~~~~

getting uploads/2017/06/Pat-Esser-Cox-150x150.jpg

getting uploads/2017/06/honorees_header2-768x432.png

 uploads/2017/06/Peter-Rice-Fox-768x1067.jpg: remote created -> g

getting uploads/2017/06/Peter-Rice-Fox-768x1067.jpg

 uploads/2017/01/team-meeting-768x691.jpg: remote created -> g

getting uploads/2017/01/team-meeting-768x691.jpg

 uploads/2017/06/Robert-Stanzione-ARRIS-150x150.jpg: remote created -> g

 uploads/2017/07/HBO?-Blacklogo.png: remote created -> g

getting uploads/2017/06/Robert-Stanzione-ARRIS-150x150.jpg

getting uploads/2017/07/HBO?-Blacklogo.png

abort: Illegal byte sequence: /Users/rngo/Desktop/Projects/wp-walterkaitz2016-content/uploads/2017/07/HBO?-Blacklogo.png

 uploads/2017/06/Rocco-Commisso-Mediacom.jpg: remote created -> g

getting uploads/2017/06/Rocco-Commisso-Mediacom.jpg​

~~~~~

[Ana Retamal]

Hi @RomeoQNgo, for what I understand, you're not having an issue with any of our products. If you're having an unrelated issue, I'm afraid we won't be able to help you as this is an Atlassian forum. You'll need to turn to Mac support or HG forums for more help with this issue, as I don't have the tools to troubleshoot that.

If you have any questions related to Atlassian products, let us know and we'll be glad to help :)

Best regards!

Ana

[Emanuel Alvaredo]

Hello @RomeoQNgo, I have the same issue, could you solve this issue?

[RomeoQNgo]

@Emanuel Alvaredo. This is a really weird issue.  It only happen on one Windows Azure VM.  The repo works fine everywhere else.

I duplicate the repo to a new BitBucket repo and was able to download on the same Azure VM and it works fine.

Then I make a space commit on the original repo and it still has the issue.

So I stripped the latest commit and then recommit with the same files change (just a merge to the default from another branch).  This time it works fine.  

So the issue is not with the file changes but something in the commits.  The commit comment is the same.

Since this is a one off happening on one random Machine, I just let treat it as a hiccup.  If this occurs again, then it is definitely worth look into.

I hope this helps.  Good Luck with your issue.

[Juan Pablo Gardella]

It's a mercurial issue https://bz.mercurial-scm.org/show_bug.cgi?id=5762