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

fix: use open_ambient_dir instead of fs::File::open to load folders #136

Merged
merged 1 commit into from
May 25, 2023

Conversation

Angelmmiguel
Copy link
Contributor

This PR fixes the issue when opening folders in Windows environments. Before, wws was using fs::File::open to open the directories for building the WasiContext. This approach worked properly on both Linux and MacOS, but was failing on Windows.

Now, wws open the directories with the Dir::open_ambient_dir method as the official Wasmtime CLI does.

From now on, these kind of errors will raise an error in the e2e tests (#134).

It closes #135

@Angelmmiguel Angelmmiguel added the 🐛 bug Something isn't working label May 24, 2023
@Angelmmiguel Angelmmiguel added this to the v1.1.2 milestone May 24, 2023
@Angelmmiguel Angelmmiguel requested a review from a team May 24, 2023 16:42
@Angelmmiguel Angelmmiguel self-assigned this May 24, 2023
Copy link
Contributor

@ereslibre ereslibre left a comment

Choose a reason for hiding this comment

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

Great finding! LGTM

Copy link
Contributor

@gzurl gzurl left a comment

Choose a reason for hiding this comment

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

Awesome!! LGTM 👍

@Angelmmiguel Angelmmiguel merged commit 40c6405 into main May 25, 2023
@Angelmmiguel Angelmmiguel deleted the 135-open-folders-in-windows branch June 30, 2023 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working cla-not-required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JavaScript workers are not properly working on Windows
4 participants