-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support Ruby 2.6.0-preview2 and Rails 5.2.1. #51
Comments
@phyllisstein it's in the pipeline - I'll try to get through it this week. Which is higher priority for you?
? |
Thanks so much! I guess my personal preference depends on what the current supported versions are, but off the top of my head I'd probably say Rails. |
Supporting Rails 5.2 would be the highest priority for me since Ruby 2.6 is not yet released and Rails 5.2 has been out for a while. |
Any update on this? Would love to take this gem for a spin, but I'm running on Rails 5.2 (w/ Ruby 2.5). |
Does this gem/Heroku add-on currently work with Ruby 2.6.2 and Rails 5.2.2? We used this gem in the past, about two years ago, and then it worked fine. However, we suddenly seem to have lost our GC configuration (stored in ENV variables) and starting new recordings doesn't work (the new recordings don't show up, not even when stopping the measurement). Might also have to do something with the upgrade to heroku-18 stack. @methodmissing is this gem still supported with new versions of Rails, Ruby, Heroku and Puma (#32, #49)? |
yeah this doesn't seem to be working for me at all on heroku with rails 5.2 and ruby 2.6.5. Fails silently, no error message, just says as soon as data is available I'll be able to manage suggested configurations. |
Hey there! After quite a struggle with Kubernetes' container termination patterns, I've finally managed to get TuneMyGC to sync my app's snapshots. Which is very exciting, but for the fact that I get an error message on sync:
Are there any plans to support Ruby 2.6.0 and/or Rails 5.2.1 in the near future? Thanks in advance for your guidance!
The text was updated successfully, but these errors were encountered: