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

Figure out wasm type errors popping up on a mac. #1241

Open
ruseinov opened this issue Aug 26, 2024 · 3 comments
Open

Figure out wasm type errors popping up on a mac. #1241

ruseinov opened this issue Aug 26, 2024 · 3 comments

Comments

@ruseinov
Copy link
Collaborator

ruseinov commented Aug 26, 2024

This has only been confirmed on a Mac with an Apple chip so far.

After the near-workspaces = "0.12" update store performance tests started throwing errors.

"Link Error: \"function types incompatible: expected func of type `(i64) -> ()`, found func of type `(i32) -> ()`\"")) })) }

The problem does not present itself on near-workspaces = "0.11". This deserves thorough investigation.

I've seen people facing similar errors on the net. Unsure if this is related, gotta dig into the changesets to figure that out.

@KevinMB0220
Copy link

I’m Kevin from Dojo Coding, and I would like to propose a solution for the issue related to the type compatibility error in near-workspaces = "0.12". My approach involves investigating the differences in function implementations between versions 0.11 and 0.12, focusing on function signatures and changes in type handling. I would also test explicit type conversions to ensure compatibility. I am committed to conducting a thorough analysis and proposing fixes to maintain stability across all platforms, including Macs with Apple chips.

@Sravya-212
Copy link

@ruseinov I want to work on this

Copy link

onlydustapp bot commented Sep 11, 2024

Hey @Sravya-212!
Thanks for showing interest.
We've created an application for you to contribute to near-sdk-rs.
Go check it out on OnlyDust!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants