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

Fixes #922 - Correctly define file encoding as UTF-8 #924

Merged
merged 1 commit into from
Mar 7, 2016

Conversation

tbrisker
Copy link
Contributor

@tbrisker tbrisker commented Mar 6, 2016

Line 103 contains the unicode character ñ which causes this to break rake for ruby 1.9.3.
Specifying the encoding for the file fixes this error.

Line 103 contains the unicode character ñ which causes this to break rake for ruby 1.9.3. 
Specifying the encoding for the file fixes this error.
@pglombardo
Copy link

Great on the quick fix. I just hit this in my travis tests if an example is needed.

@deepj
Copy link
Contributor

deepj commented Mar 6, 2016

Unfortunately, Puma supports only Ruby 2.1 and later now. See b4a2fde.

@pglombardo
Copy link

Ah ok that's understandable. The gemspec should probably be updated to reflect that as well then. Thanks!

evanphx added a commit that referenced this pull request Mar 7, 2016
Fixes #922 - Correctly define file encoding as UTF-8
@evanphx evanphx merged commit 4ca8123 into puma:master Mar 7, 2016
tbrisker added a commit to tbrisker/rake that referenced this pull request Mar 8, 2016
TraceOutput#trace_on has a bug that causes the matching to fail if a
string is incorrectly encoded, for example encoded as 'US-ASCII' but
contains unicode characters. This causes a new exception to be thrown,
losing the stack trace of the previous exception.
This can occur, for example, in Ruby 1.9 when one of the dependencies of
a project includes a file that contains unicode but does not specify an
encoding (as the default for Ruby 1.9 is US-ASCII). This was the case in
a certain version of the Puma web server, which was fixed in
puma/puma#924 but was very difficult to debug due
to the incorrect stack trace provided by rake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants