Skip to content

syscall: js/wasm file operations fail on windows / node.js [1.24 backport] #71977

Closed
@gopherbot

Description

@gopherbot

@dmitshur requested issue #71758 to be considered for backport to the next 1.24 minor release.

@gopherbot Please add this issue for us to consider for backport to 1.24.

I can be convinced otherwise, but not sure if this meets the bar: the experimental js/wasm port is intended to run in browsers, and uses Node only for testing. This breaks testing support on a Windows host. On the other hand, the backport is very safe and there's no workaround for the affected environment other than modifying the files manually.

Activity

added this to the Go1.24.1 milestone on Feb 26, 2025
added
TestingAn issue that has been verified to require only test changes, not just a test failure.
on Feb 26, 2025
gopherbot

gopherbot commented on Feb 26, 2025

@gopherbot
ContributorAuthor

Change https://go.dev/cl/652835 mentions this issue: [release-branch.go1.24] syscall: disable O_DIRECTORY on Windows for js/wasm

gopherbot

gopherbot commented on Feb 26, 2025

@gopherbot
ContributorAuthor

Closed by merging CL 652835 (commit 4070531) to release-branch.go1.24.

added a commit that references this issue on Feb 26, 2025
4070531
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CherryPickApprovedUsed during the release process for point releasesTestingAn issue that has been verified to require only test changes, not just a test failure.compiler/runtimeIssues related to the Go compiler and/or runtime.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @prattmic@dmitshur@gopherbot

        Issue actions

          syscall: js/wasm file operations fail on windows / node.js [1.24 backport] · Issue #71977 · golang/go