zigup icon indicating copy to clipboard operation
zigup copied to clipboard

Freshly-installed `zigup` fails to run `zigup master` twice, third time works

Open cr1901 opened this issue 3 years ago • 0 comments

Context

My zigup was built using zig build -Dtarget=x86_64-windows-gnu on a Linux machine running Ubuntu 20.04, using zig commit 0e6d2184c.

William@DESKTOP-H0PMN4M C:\Users\William\zig\bin
$ zigup master
install directory 'C:\Users\William\zig\bin\zig'
mkdir "C:\Users\William\zig\bin\zig"
rd /s /q "C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing"
mkdir "C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing"
downloading 'https://ziglang.org/builds/zig-windows-x86_64-0.10.0-dev.555+1b6a1e691.zip' to 'C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing\zig-windows-x86_64-0.10.0-dev.555+1b6a1e691.zip'
extracting archive to "C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing"
extracted archive in 162.98 s
rd /s /q "C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing\zig-windows-x86_64-0.10.0-dev.555+1b6a1e691.zip"
mv 'C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing\zig-windows-x86_64-0.10.0-dev.555+1b6a1e691' 'C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing\files'
mv 'C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing' 'C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691'
error: AccessDenied
Unable to dump stack trace: FileNotFound

William@DESKTOP-H0PMN4M C:\Users\William\zig\bin
$ zigup master
install directory 'C:\Users\William\zig\bin\zig'
mkdir "C:\Users\William\zig\bin\zig"
rd /s /q "C:\Users\William\zig\bin\zig\0.10.0-dev.555+1b6a1e691.installing"
error.Unexpected NTSTATUS=0xc0000056
Unable to dump stack trace: FileNotFound
error: Unexpected
Unable to dump stack trace: FileNotFound

Other Context

[00:20:28] <marler8997_> 0xC0000056
[00:20:28] <marler8997_> STATUS_DELETE_PENDING
[00:21:11] <cr1901> Also a probably related error: AccessDenied

Other Info

The third attempt of running zigup master succeeded, but I didn't capture the stdout of that before cls the command prompt (oops!). No errors were reported.

cr1901 avatar Feb 05 '22 05:02 cr1901