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

undefining the allocator of T_DATA class ... warning on Ruby 3.2 #74

Open
eric-hemasystems opened this issue Jun 28, 2023 · 0 comments
Open
Labels
🐞 bug Something isn't working

Comments

@eric-hemasystems
Copy link

Describe the bug

In Ruby 3.2 all the wasmer classes when creating an instance now show a warning similar to:

warning: undefining the allocator of T_DATA class Wasmer::Store

It's not just Wasmer::Store that does this but I also see it on Wasmer::Module, Wasmer::Wasi::StateBuilder, Wasmer::Wasi::Environment and Wasmer::ImportObject.

Steps to reproduce

% irb
irb(main):001:0> require "wasmer"
=> true
irb(main):002:0> Wasmer::Store.new
(irb):2: warning: undefining the allocator of T_DATA class Wasmer::Store

Expected behavior

The instance should be created without a warning.

Actual behavior

I get a warning. It can be suppressed via $VERBOSE (or Rails' silence_warnings which is a wrapper for $VERBSOSE). The actual functionality seems to all work just fine.

Additional context

I was previously using Ruby 3.0.4 and did not get a warning with that version.

@eric-hemasystems eric-hemasystems added the 🐞 bug Something isn't working label Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant