-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Dump outer variables tables when dumping an iseq to binary #4942
Conversation
Another minor thing, I think you want to bump |
Ya, I mentioned in the RedMine ticket, but I wasn't actually sure what needed to change. I'll fix it now. 🙇 |
This commit dumps the outer variables table when dumping an iseq to binary. This fixes a case where Ractors aren't able to tell what outer variables belong to a lambda after the lambda is loaded via ISeq.load_from_binary [Bug #18232] [ruby-core:105504]
d8c5a23
to
15c9460
Compare
Since this commit has been merged to the master branch, Rails Active Job integration with async adapter has been failing. https://buildkite.com/rails/rails/builds/81621#8a717e31-68fb-4014-b6ea-f0311db37182/1076-1097
|
@yahonda thanks! I'll take a look |
@yahonda I fixed it. It's really really weird, but the source of the actual bug is that anonymous parameters have no name. I filed a redmine issue here: https://bugs.ruby-lang.org/issues/18250 Also a PR here |
Thanks for the fix. Let me test it again once #4961 is merged to Ruby master branch. |
This commit dumps the outer variables table when dumping an iseq to
binary. This fixes a case where Ractors aren't able to tell what outer
variables belong to a lambda after the lambda is loaded via ISeq.load_from_binary
[Bug #18232] [ruby-core:105504]