-
Notifications
You must be signed in to change notification settings - Fork 144
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
Compatibility in ruby >=3.2 ? #233
Comments
This would only ever fire if you’ve got a syntax error or are trying to load a file that doesn’t exist. if someone wants to remove dead-end or upgrade it to syntax_suggest I would accept the change. |
(possibly) addresssed by #228 which replaces |
Hi @Jaco-Pretorius as @schneems mentioned, this doesnt appear to be a dead_end/syntax_suggest issue and the main branch now has coverage for ruby 3.2 specifically. Since #230 already tracks the dead_end migration work I'll close this for now. Please reopen with repro steps against the latest derailed if you still believe there's a bug here. Thanks! |
For the record, I am experiencing a similar issue with Ruby 3.1.3 and derailed_benchmark 2.2.1
|
Can you provide a minimal repro please? Your output suggests that syntax_suggest is missing from bundle path but its not clear what command you’re running or how things are set up |
I just ran into the same error in 3.1.2. I'm guessing the group :development do
...
gem "syntax_suggest" # <-- added this
gem "derailed_benchmarks"
gem "stackprof"
...
end |
I think an issue is the conditional in the gemspec. If you look at the dependencies on rubygems it doesn't list out syntax_suggest https://rubygems.org/gems/derailed_benchmarks/versions/2.2.1. It works with Ruby 3.2+ on CI because that gem exists |
The intent of the conditional was to avoid declaring |
Sounds good to me
Richard Schneeman
https://howtoopensource.dev
https://www.schneems.com
he/him
…On Sat, Nov 16, 2024 at 2:20 PM Peter Cai ***@***.***> wrote:
The intent of the conditional was to avoid declaring syntax_suggest for
ruby versions where it is already a default gem, but if there's no harm in
declaring it unconditionally -- I'll just make that change? wdyt @schneems
<https://github.com/schneems>
—
Reply to this email directly, view it on GitHub
<#233 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOSYAF2NEABWUUX7TE5NL2A6SHHAVCNFSM6AAAAABAX6VFM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQG44DKNJVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I am having issues with running derailed against a Rails app with Ruby 3.2.2. The issue is rather obscure, but I'll put the stacktrace here
I suspect this is because the
dead_end
gem - which is thesyntax_suggest
repo - has been integrated with Ruby 3.2. At the very least it's not clear to me what is expected to happen if you include that gem while running Ruby 3.2 or later. There is an issue against thesyntax_suggest
repo which seems to indicate that you no longer need to include the gem but it doesn't say what will happen when you do. The stacktrace above does point to some of therequire_relative
overrides going on in that gem.The text was updated successfully, but these errors were encountered: