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
Ruby 2.4.0 bug 12782 #909
Comments
We have API exactly for this problem #896. I'll use it for Haml 5 and fix it in another way in Haml 4, considering Haml 4 is already in stable branch. |
Don't port this forward to Haml 5. Use after_preamble option in precompiled_with_ambles instead. close #909.
Fixed this in stable branch ac290b5. Please wait for new 4.0.x release. And for Haml 5, I opened rtomayko/tilt#312. Since there's nothing to do in Haml side, closing this issue. |
Thanks, much appreciated. |
It seems like there has never been another 4.0.x release? Or am I missing something? (I would like to move to 5 but have not been able to yet because it breaks my app #770 ) Edited to add: Just noticed the addition of |
@k0kubun ac290b5 was deleted. Any other suggestions? Can it be resurrected by any chance? @ireneybean Did you manage to migrate to haml 5.x? Does |
Don't port this forward to Haml 5. Use after_preamble option in precompiled_with_ambles instead. close haml#909. Backported from haml@ac290b5
@x-yuri Yes! We're currently running with haml-5.1.2 and using |
We don't support Haml 4 as it was released over 4 years ago. We will continue to support Haml 5 until Haml 6 is fully released. Sorry! |
Yes, what about it? WIll upgrading
It's not about support. Supposedly the I'm not a developer, not in this case. And upgrading the major version not knowing the code... I'd prefer the developer to handle it. Hopefully with the feedback from ireneybean that would be easy. |
Cross posting Tilt issue #311 as it's relevant here too (unless you say otherwise)
Hi,
I've just upgraded to Ruby v2.4.0 and appear to have been bitten by the bug described on the Ruby bug tracker.
They appear to have decided to revert the change that caused it, but to add warnings, probably to nudge people to stop forwarding to private methods. I thought I'd be helpful and open this issue ahead of time. Or for it to be fixed immediately (no pressure;)
Regards,
iain
ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin13]
Tilt v2.0.6
Haml v4.0.7 and 5.0.0.beta.2
The text was updated successfully, but these errors were encountered: