-
Notifications
You must be signed in to change notification settings - Fork 183
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
Error loading ISeq from cache for sass-3.4.23 #30
Comments
It's odd that this would happen on the first run. I've seen this occasionally internally at Shopify and never been able to track down exactly how it's able to desync the key and value like this. I don't have a solution off the top of my head. I'll try to debug it more thoroughly next time someone in the same building as me has this problem. |
🤙
[Joshua Powell - Contact Using Hop](http://GetHop.com/?_hmid=1494518998)
On May 11, 2017 at 15:47 GMT, Burke Libbey <notifications@github.com> wrote:
It's odd that this would happen on the first run. I've seen this occasionally internally at Shopify and never been able to track down exactly how it's able to desync the key and value like this. I don't have a solution off the top of my head. I'll try to debug it more thoroughly next time someone in the same building as me has this problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#30 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGa7XuGdmFJDQ9fIvDiNRzdDMUo5uHzBks5r4y1zgaJpZM4NXLW1).
|
Cache implementation is completely changed now, so I don't expect this to recur with 0.3.0+ |
Hi @burke! Thanks for this project. On my first try, it yelled back at me.
The 'fix' got me to the next gem with a similar issue. Please let me know if this is too much info.
I'll submit a separate issue for each gem I run into a similar issue with.
Details below:
results from:
=
results from:
=
here's the full trace:
The text was updated successfully, but these errors were encountered: