Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

wasm-bindgen-cli extraction never completes if the crate is already there #5

Open
2 of 3 tasks
wooferzfg opened this issue Apr 20, 2020 · 1 comment
Open
2 of 3 tasks
Labels
bug Something isn't working

Comments

@wooferzfg
Copy link

wooferzfg commented Apr 20, 2020

Do the checklist before filing an issue:

Description

It seems like a prompt is coming up if the crate already exists in .cargo/bin, which causes the action to never finish.

Used environment

Workflow code

https://github.com/CryZe/LiveSplitOne/blob/275b166098503f174a38965243a74e56cc6c4792/.github/workflows/ci.yml#L62

Action output

https://github.com/LiveSplit/LiveSplitOne/runs/599647150?check_suite_focus=true#step:12:20

Screenshot_20200419-211114_Chrome

Expected behavior

The ZIP file is extracted even if it's already in .cargo/bin.

@wooferzfg wooferzfg added the bug Something isn't working label Apr 20, 2020
@wooferzfg wooferzfg changed the title wasm-bindgen-cli extraction never completes if the zip file is already there wasm-bindgen-cli extraction never completes if the crate is already there Apr 20, 2020
@svartalf
Copy link
Member

@wooferzfg filed the upstream bugfix

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants