-
Notifications
You must be signed in to change notification settings - Fork 35
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
Ruby 1.9: ArgumentError: invalid byte sequence in US-ASCII #9
Comments
Btw, also this in begin of Gemfile doesn't help ;-(
|
Thanks for the bug report! I'll investigate today. |
Thank you, Matt. |
@mattbrictson - i tried it, but it doesn't help :-( After Gemfile update, i run
and Current trace is the same:
|
@janreges The stack trace you posted is an error in Rake itself, which is making troubleshooting difficult. Rake seems to have caught an exception, but is encountering its own error when attempting to handle that exception. As a result, the original exception is getting lost. Is there any way you could use a debugger, add some |
@mattbrictson: i'm not a ruby/rails programmer, but this was simple :) I added In deploy, an exception below has been thrown. After that, i looked into When i added encoding manually, everything is working fine. So, it's my fail. Probably still something else was needed, except
|
@janreges Great! I think you did everything right, except maybe you ran just |
Fixed in e5236dc. |
@mattbrictson Your guess was right :-) I ran "cap" instead of "bundle exec cap". Thank you for your support! |
Hi,
when i installed airbrussh, my
cap production deploy
ends with trace below.I tried to add
#encoding: utf-8
into "deploy.rb", or add toLANG="en_US.UTF-8"
andLC_ALL="en_US.UTF-8"
into "Gemfile", but it doesn't help.Thank you for your suggestions, how to fix it.
The text was updated successfully, but these errors were encountered: