-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
JRuby-Head, Rails 4.1.9, and Sass 3.4.13 throws bad value for range #2786
Comments
I have not looked into this past looking at what tok() is but it points back to strscan and we have had a ton of M17n activity lately. It would be really nice if you could figure out what the source it is choking on while parsing. As this issue is written up we just know sass is barfing on some bad data (no doubt from us providing some mangled data to sass). If you could puts the data it is parsing then it will be much easier for us to fix. |
I'll dig into it a bit further. Al I know atm is that it seems to be something in Bourbon/Neat. Where should I throw the a |
@Ch4s3 I am not entirely sure. I will just dump what I would first try...The parser where it is throwing can probably be a good place to see the troubled str in question which strscan is looking at. From there perhaps you can find the original source data to see how it changed. I suspect this can be reduced to using strscan + some read in source data. |
I'm going to have to pull down the Sass gem and pry into it later. |
Do you have a way for us to reproduce this? |
I'll post a repo as soon as(if) I can reproduce it in isolation. So far, it seems particular to my production app. |
I will take some time today to make sure we're running all strscan tests/specs we can. |
I don't see a sass 5.0.1...are you sure about that version? |
Sorry, that was a copy/paste error on my part. I'm using |
I twiddled StringScanner and got all tests running, but I didn't see anything major that might explain your issue. |
It might be fairly specific to my app's setup, I tried to reproduce it yesterday for an hour or so on a fresh app, and couldn't. I'm perfectly happy waiting for pre2 to release and seeing if the issue persists. |
Ok...I'm going to close this as invalid for now. If you can come up with a reproduction, feel free to reopen. |
Sounds good. |
This happens on head but not on 9k-pre1.
The text was updated successfully, but these errors were encountered: