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

[WASM] Fix third parameter marshaling on callbacks #101638

Merged

Conversation

maxkatz6
Copy link
Contributor

This reason of the issue seems to be a simple typo. On top of that adding a unit tests.

Note, I didn't figure out how to build wasm unit tests locally yet, so hopping for CI to help here.
Let me know, if I am missing anything.

Fix #101637

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)
Copy link
Member

@lewing lewing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this.

@lewing lewing merged commit 55d2ada into dotnet:main Apr 27, 2024
32 of 37 checks passed
am11 pushed a commit to am11/runtime that referenced this pull request Apr 27, 2024
* Fix typo with get_signature_arg3_type incrorrecty arg2 instead of arg3

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)

* Add another callback tests to cover different parameter types
am11 pushed a commit to am11/runtime that referenced this pull request Apr 27, 2024
* Fix typo with get_signature_arg3_type incrorrecty arg2 instead of arg3

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)

* Add another callback tests to cover different parameter types
matouskozak pushed a commit to matouskozak/runtime that referenced this pull request Apr 30, 2024
* Fix typo with get_signature_arg3_type incrorrecty arg2 instead of arg3

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)

* Add another callback tests to cover different parameter types
@pavelsavara
Copy link
Member

Thank you!

michaelgsharp pushed a commit to michaelgsharp/runtime that referenced this pull request May 9, 2024
* Fix typo with get_signature_arg3_type incrorrecty arg2 instead of arg3

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)

* Add another callback tests to cover different parameter types
Ruihan-Yin pushed a commit to Ruihan-Yin/runtime that referenced this pull request May 30, 2024
* Fix typo with get_signature_arg3_type incrorrecty arg2 instead of arg3

get_signature_arg3_type method is expected to read argument type by Arg3MarshalerType (=28) offset instead of Arg2MarshalerType (=24)

* Add another callback tests to cover different parameter types
@github-actions github-actions bot locked and limited conversation to collaborators Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Runtime.InteropServices.JavaScript community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[WASM] Issues with callback parameters marshaling
3 participants