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

Ruby 2.4.0 bug 12782 #909

Closed
yb66 opened this issue Mar 23, 2017 · 9 comments
Closed

Ruby 2.4.0 bug 12782 #909

yb66 opened this issue Mar 23, 2017 · 9 comments

Comments

@yb66
Copy link

yb66 commented Mar 23, 2017

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.

myproj/vendor/ruby/2.4.0/gems/tilt-2.0.6/lib/tilt/haml.rb:50:in `block in precompiled_postamble': Haml::Engine#precompiled_method_return_value at /opt/rubies/ruby-2.4.0/lib/ruby/2.4.0/forwardable.rb:156 forwarding to private method Haml::TempleEngine#precompiled_method_return_value

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

@k0kubun
Copy link
Member

k0kubun commented Mar 23, 2017

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.

k0kubun added a commit that referenced this issue Mar 28, 2017
Don't port this forward to Haml 5. Use after_preamble option in
precompiled_with_ambles instead.

close #909.
@k0kubun
Copy link
Member

k0kubun commented Mar 28, 2017

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.

@k0kubun k0kubun closed this as completed Mar 28, 2017
@yb66
Copy link
Author

yb66 commented Mar 28, 2017

Thanks, much appreciated.

@ireneybean
Copy link

ireneybean commented Sep 13, 2020

Fixed this in stable branch ac290b5. Please wait for new 4.0.x release.

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 options.escape_filter_interpolations ... That'll work.

@x-yuri
Copy link

x-yuri commented Aug 3, 2021

@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 options.escape_filter_interpolations help in this regard?

x-yuri added a commit to x-yuri/haml that referenced this issue Aug 3, 2021
 Don't port this forward to Haml 5. Use after_preamble option in
 precompiled_with_ambles instead.

 close haml#909.

 Backported from haml@ac290b5
@ireneybean
Copy link

@x-yuri Yes! We're currently running with haml-5.1.2 and using options.escape_filter_interpolations set to false with no problems.

@k0kubun
Copy link
Member

k0kubun commented Aug 3, 2021

@k0kubun ac290b5 was deleted.

I don't get what you mean. Did you read the message of the commit? Haml 5.x and some newer versions of Tilt should work. Consider upgrading your Tilt.

If you're talking about Haml 4 releases, please consult @hcatlin. I simply don't have permission for fixing it.

@HamptonMakes
Copy link
Member

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!

@x-yuri
Copy link

x-yuri commented Aug 3, 2021

Did you read the message of the commit?

Yes, what about it? WIll upgrading tilt let me stay with haml 4.x?

We don't support Haml 4 as it was released over 4 years ago.

It's not about support. Supposedly the stable branch was deleted, which had some useful commits. I was able to restore it though.

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.

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

No branches or pull requests

5 participants