8000 Additional checking for wasm32-wasi output from Rust projects. by kpfleming · Pull Request #1458 · fastly/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Additional checking for wasm32-wasi output from Rust projects. #1458

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

Closed
wants to merge 1 commit into from

Conversation

kpfleming
Copy link
Contributor
@kpfleming kpfleming commented Apr 9, 2025

In version 11.0.0 a test was added to ensure that the CLI's global configuration file was not configured for 'wasm32-wasi' output from Rust projects. That was insufficient to avoid build errors in existing projects configured for that target, so this commit adds an additional check. Specifically, if the WASM binary is not found in the expected location after a successful build, a check is made to see if the binary is found in the 'old' location. If it is found there, an error is emitted which includes a link to the instructions for how to reconfigure the project.

NOTE: The URL in this PR is not yet live; it will be once a PR to our documentation site has been merged.

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

  • Does your submission pass tests?

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully run tests with your changes locally?

User Impact

  • What is the user impact of this change? - a new error will be generated for Rust projects which have not been upgraded

Are there any considerations that need to be addressed for release?

In version 11.0.0 a test was added to ensure that the CLI's global
configuration file was not configured for 'wasm32-wasi' output from
Rust projects. That was insufficient to avoid build errors in existing
projects configured for that target, so this commit adds an additional
check. Specifically, if the WASM binary is not found in the expected
location after a successful build, a check is made to see if the
binary is found in the 'old' location. If it is found there, an error
is emitted which includes a link to the instructions for how to
reconfigure the project.
@kpfleming kpfleming marked this pull request as ready for review April 9, 2025 22:13
@kpfleming kpfleming requested a review from a team as a code owner April 9, 2025 22:13
@kpfleming kpfleming requested a review from philippschulte April 9, 2025 22:13
Copy link
Member
@philippschulte philippschulte left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you!

@kpfleming
Copy link
Contributor Author

I'm going to recreate this PR as GitHub hasn't processed the last push yet, and it's been 12 hours.

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

Successfully merging this pull request may close these issues.

2 participants
0