Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid US-ASCII character "\xC3" in singularitygs-1.6.2/stylesheets/singularitygs/helpers/_str-replace.scss #207

Closed
cyberswat opened this issue Feb 27, 2015 · 16 comments
Labels

Comments

@cyberswat
Copy link

My monitoring awoke me to this .. any chance you can help me correlate what was in your release yesterday that would cause this?

[31m error[0m scss/print.scss (Line 7 of /retracted/shared/bundle/ruby/1.9.1/gems/singularitygs-1.6.2/stylesheets/singularitygs/helpers/_str-replace.scss: Invalid US-ASCII character "\xC3")
[31m error[0m scss/style.scss (Line 7 of /retracted/shared/bundle/ruby/1.9.1/gems/singularitygs-1.6.2/stylesheets/singularitygs/helpers/_str-replace.scss: Invalid US-ASCII character "\xC3")
[31mCompilation failed in 2 files.

@cyberswat
Copy link
Author

@Snugug any help understanding what I'm dealing with here would be fantastic.

@cyberswat
Copy link
Author

@cyberswat
Copy link
Author

[root@web01 cyberswat]# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

@Snugug
Copy link
Member

Snugug commented Feb 27, 2015

There is a comment on line 7 of the string replace helper that includes someone's name that has an é in it. That appears to be the problem you're running into as it's not a US character.

https://github.com/at-import/Singularity/blob/1.x.x/stylesheets/singularitygs/helpers/_str-replace.scss#L7

On Feb 27, 2015, at 7:48 AM, Kevin Bridges notifications@github.com wrote:

My monitoring awoke me to this .. any chance you can help me correlate what was in your release yesterday that would cause this?

[31m error[0m scss/print.scss (Line 7 of /retracted/shared/bundle/ruby/1.9.1/gems/singularitygs-1.6.2/stylesheets/singularitygs/helpers/_str-replace.scss: Invalid US-ASCII character "\xC3")
[31m error[0m scss/style.scss (Line 7 of /retracted/shared/bundle/ruby/1.9.1/gems/singularitygs-1.6.2/stylesheets/singularitygs/helpers/_str-replace.scss: Invalid US-ASCII character "\xC3")
[31mCompilation failed in 2 files.


Reply to this email directly or view it on GitHub.

@cyberswat
Copy link
Author

awesome .. that was super helpful.

@Snugug
Copy link
Member

Snugug commented Feb 27, 2015

That resolve this issue?

@cyberswat
Copy link
Author

My challenge is that I don't do development with this gem or sass. I've reverted our systems to version 1.5.1 that does not have this issue and am restoring the deployments affected by this. We picked this up in a testing environment so it was caught relatively early.

I do agree with you that the character in that comment is the culprit. From what I could tell the encoding on the server is set properly and explicitly setting it in the file that is invoking singularity did not resolve the issue.

I'll get someone to look at this this morning.

@Snugug
Copy link
Member

Snugug commented Feb 27, 2015

Sounds good, keep me posted. FWIW that character has no impact on actually being able to use the code in that file (assuming you can get past the encoding error you seem to be having).

@aliyakhan
Copy link

any update here? Getting same issue.

@Snugug
Copy link
Member

Snugug commented Mar 3, 2015

If you can, I recommend using utf-8 instead of us-ascii for Singularity (really in general), but I'll look into pushing a point release today that removes the non-us-ascii character

@aliyakhan
Copy link

Yeah did that already. Thx

@GuyPaddock
Copy link

Any updates on this issue? We just started seeing it as well.

@Arvoreen
Copy link

I was able to get past this by adding the following line to the end of my config.rb file:

Encoding.default_external = 'UTF-8'

@rmcveigh
Copy link

rmcveigh commented Aug 3, 2015

Adding Encoding.default_external = 'UTF-8' to my config.rb file worked for me as well. Thanks Arvoreen.

@shawnzhu
Copy link

@Arvoreen 's fix works for me as well

@alvinpascoe
Copy link

Excellent, thanks @Arvoreen. Works great for me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants