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

Encoding::CompatibilityError #57

Closed
brynary opened this issue Aug 24, 2012 · 4 comments
Closed

Encoding::CompatibilityError #57

brynary opened this issue Aug 24, 2012 · 4 comments
Assignees

Comments

@brynary
Copy link

brynary commented Aug 24, 2012

After upgrading to a6, I get Encoding::CompatibilityErrors...

incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)

Error Backtrace /data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_lexer.rb:1246:in `check'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_lexer.rb:1246:in `block in yylex'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_lexer.rb:678:in `loop'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_lexer.rb:678:in `yylex'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_lexer.rb:92:in `advance'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_parser_extras.rb:874:in `next_token'
(eval):3:in `_racc_do_parse_c'
(eval):3:in `do_parse'
/data/worker/shared/bundle/ruby/1.9.1/gems/ruby_parser-3.0.0.a6/lib/ruby_parser_extras.rb:923:in `process'
/data/worker/releases/20120824192219/lib/quality/ruby/parser.rb:20:in `block in parse'
@zenspider
Copy link
Member

Any chance you can get me the repro file?

I'm not sure it'll be good for an encoding error, but bin/ruby_parse_extract_error might be able to extract just the problematic code.

@ghost ghost assigned zenspider Aug 25, 2012
@brynary
Copy link
Author

brynary commented Aug 25, 2012

I'll see what I can do. If I can find a repro in OSS code, yes. But I had
to rollback so I'll need to get .a5 and .a6 running concurrently to get
failure data from .a6. Might take awhile.

On Saturday, August 25, 2012, Ryan Davis wrote:

Any chance you can get me the repro file?

I'm not sure it'll be good for an encoding error, but
bin/ruby_parse_extract_error might be able to extract just the problematic
code.


Reply to this email directly or view it on GitHubhttps://github.com//issues/57#issuecomment-8022734.

@zenspider
Copy link
Member

On Aug 25, 2012, at 09:31 , Bryan Helmkamp notifications@github.com wrote:

I'll see what I can do. If I can find a repro in OSS code, yes. But I had
to rollback so I'll need to get .a5 and .a6 running concurrently to get
failure data from .a6. Might take awhile.

No worries if you can't get an OSS repro. I'll be setting up gauntlet soon for a 1.9 stress test.

@brynary
Copy link
Author

brynary commented Oct 15, 2012

Replaced by #72.

@brynary brynary closed this as completed Oct 15, 2012
@seattlerb seattlerb locked and limited conversation to collaborators Jan 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants