-
Notifications
You must be signed in to change notification settings - Fork 180
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
iseq.rb:13 to_binary
: wrong argument type false (expected Symbol)
#378
Comments
Hi, @zzak, this is indeed a know issue, but with MRI: https://bugs.ruby-lang.org/issues/18250 If you are currently testing ruby-head, it's best to disable ISeq caching for now. If somehow |
Actually maybe I should release it now regardless to help people who test against ruby-head. |
@casperisfine Thanks for the reply! Let me try nobu's patch :) |
To be clear, we found way more issues and it's no longer a two lines change. Make sure to use the full branch: ruby/ruby#5035 |
@casperisfine I was able to make it at least this far using the branch, so maybe we can close this one? |
We can keep it open as long as the Ruby bug isn't fixed, so that other people looking for it can find it more easily. |
It looks like this bug made it into the released ruby 3.0.3:
|
😭 Ok, I'll have to ship a workaround. Thank you for letting me know. |
I pushed a 1.9.2 release that entirely disable ISeq compilation if that bug is detected. I'll see if I can do some more finely grained workaround. |
The potential less impacting workaround: #380, I'm just worried it might cause even worse problem, so I'd like to carefully test it first. |
Updating to 1.9.3 helped us with this issue. Thanks! |
Welcome. I think we can close this now. |
bundle update bootsnap Rubyのバージョンアップにより、bootsnapがエラーする。 そのためRailsの起動ができなくなる。 bootsnap 1.9.3にて修正されている。 そのためbootsnapのバージョンを上げた。 bootsnapのIssue 378を参照 ttps://github.com/Shopify/bootsnap/issues/378
This seems to fix CI failures when ruby 3.0.3 is installed. I noticed the failures in this PR: #915 But I was able to reproduce the failures on a clean branch using ruby 3.0.3 Related: Shopify/bootsnap#378
Ruby 3.0 にアップデートするために bootsnap 1.9.3 にアップデートする ref: `Shopify/bootsnap#378
Ruby 3.0 にアップデートするために bootsnap 1.9.3 にアップデートする ref: `Shopify/bootsnap#378
This is one works |
While upgrading, I also needed to do a `bundle update bootsnap ` because there's a known issue where Ruby 3.0.3 and older Bootsnaps dislike each other very much. Shopify/bootsnap#378
Having problems when I run rails db:create using ruby 3.0.4.
|
Your backtrace shows that you are running |
When attempting to run the server on Ruby 3.0.4, it fails. Apparently, some bug was released in Ruby 3.0.3 that affects Bootsnap. However, Bootsnap released a workaround patch. Error: ``` .rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/bootsnap-1.7.5/lib/bootsnap/compile_cache/iseq.rb:13:in `to_binary': wrong argument type false (expected Symbol) (TypeError) ``` Reference: - Shopify/bootsnap#378
When attempting to run the server on Ruby 3.0.4, it fails. Apparently, some bug was released in Ruby 3.0.3 that affects Bootsnap. However, Bootsnap released a workaround patch. Error: ``` .rbenv/versions/3.0.4/lib/ruby/gems/3.0.0/gems/bootsnap-1.7.5/lib/bootsnap/compile_cache/iseq.rb:13:in `to_binary': wrong argument type false (expected Symbol) (TypeError) ``` Reference: - Shopify/bootsnap#378
When I install Ruby 3.2.2, the error comes out like this, I cannot open a normal Rails new project, I need to eliminate it, but the speed decreases this time.
|
- add babel-plugin-transform-react-remove-prop-types to shakapacker - update selenium and bigdecimal, spec ruby-3.0.4 - use a fork of active-triples to permit ruby-3 - use bootsnap ~> 1.9.3 to avoid iseq bug -- Shopify/bootsnap#378
- add babel-plugin-transform-react-remove-prop-types to shakapacker - update selenium and bigdecimal, spec ruby-3.0.4 - use a fork of active-triples to permit ruby-3 - use bootsnap ~> 1.9.3 to avoid iseq bug -- Shopify/bootsnap#378
- add babel-plugin-transform-react-remove-prop-types to shakapacker - update selenium and bigdecimal, spec ruby-3.0.4 - use a fork of active-triples to permit ruby-3 - use bootsnap ~> 1.9.3 to avoid iseq bug -- Shopify/bootsnap#378
Ruby 3.0.3+ appears to ship with a bug which causes bootsnap to crash. Bootsnap 1.9.2 works around this by disabling compilation caching if the bug is detected. Subsequent versions improve upon this workaround. The latest release still officially supports Ruby 3.0, so I've decided to upgrade to that. Read more: - Shopify/bootsnap#378 - https://github.com/Shopify/bootsnap/blob/main/CHANGELOG.md#192 - https://bugs.ruby-lang.org/issues/18250
Having issues with bootsnap on a
rails new --main
application using ruby-dev 3.1.0:The same thing happened before trying the
github: "Shopify/bootsnap"
, just wondering if this is a known issue or I'm missing something 🤔The text was updated successfully, but these errors were encountered: