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 byte sequence in US-ASCII : report the wrongly encoded file #12041
Comments
I think you use ruby 1.9.3. Please try to add |
Thanks for such quick reply. Yes I use Ruby 1.9.3 and Rails 3.2 I actually fixed it already (I should have mentionned it in the . Here is the stackoverflow post refering the problem : http://stackoverflow.com/questions/18467786/rails-invalid-byte-sequence-in-us-ascii But what I'm reporting here is that the error message should be more verbose, and mentionning the error's filename or even better line number. What do you reckon ? |
This is not a Rails error message, it is Ruby that is giving you this error. If you want a more verbose error message you should file a Ruby issue. |
Yup, ok thanks! |
One question. If you have the application stopped and run the rails server will the application boot? |
Yes, it does boot. 2013/8/27 Rafael Mendonça França notifications@github.com
|
I see. If you try to boot the application in the production environment of even on the test environment I think it will not boot and maybe it will give you a better error message. |
Indeed :
But who could dare trying in production what doesn't work in development? |
In test you will get the same result, or even in development if you enable the eager loading. |
It took me hours to solve this error:
having no other information about where the error came from.
Can't ruby/rails report the filename when this issue arises?
(In my case, it was in one of the application helpers ...)
Or am I lacking of experience in Rails to debug this super quickly?
The text was updated successfully, but these errors were encountered: