Skip to content

Conversation

@dscho
Copy link
Collaborator

@dscho dscho commented Mar 30, 2021

D'oh! In my recent workaround, I totally forgot that on Windows, /tmp is not equal to /tmp...

This fixes that, and it also adds a (manual) workflow that can be used for interactive testing.

This fixes #67

dscho added 3 commits March 30, 2021 12:39
This adds a GitHub workflow that can be triggered manually, executing
the GitHub Action in a multitude of scenarios.

Signed-off-by: Johannes Schindelin <[email protected]>
The `tmate` we use on Windows is compiled using MSYS2, which has a very
specific idea where `/tmp/` is: it internally translates Unix-style
absolute paths into absolute Windows paths, and that is different from
what node.js does: `/tmp/` translates to `C:/tmp/`, while MSYS2
interprets `/tmp/` as `C:/msys64/tmp/`.

Let's execute a shell command to write the temporary `bashrc` file so
that it lands in the location expected by our `tmate` invocation.

This fixes mxschmitt#67

Signed-off-by: Johannes Schindelin <[email protected]>
Signed-off-by: Johannes Schindelin <[email protected]>
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.

When running on windows-2019 worker: Error: ENOENT: no such file or directory, open '/tmp/tmate.bashrc' during tmate install

2 participants