cargo emits error when run in sandboxie

[retep998]

After nearly any command completes:

thread 'main' panicked at 'assertion failed: list.len() > 0', src\tools\cargo\src/cargo\util\job.rs:166:12
stack backtrace:

It still builds or runs whatever I ask, but it always emits that error when its done.

For those who don't know, sandboxie is a sandboxing thing for Windows, which is really important when building random untrusted projects off the internet which could execute arbitrary build scripts and pwn your computer.

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[retep998]

It's much worse now, because now cargo refuses to work outright!

> cargo build
   Compiling winapi v0.3.5 (file:///C:/Users/Peter/Code/winapi-rs)
error: failed to build archive: permission denied

error: aborting due to previous error

thread 'main' panicked at 'assertion failed: list.len() > 0', tools\cargo\src/cargo\util\job.rs:179:13
stack backtrace:

[Eh2406]

Thanks to the stale bot for reminding me that this exists. Sorry that it has not been addressed already.

I am a contributor to cargo and a windows based lifeform, but I have know idea how to get started on addressing this. I had not heard on sandboxie before this issue. How does one start debugging problems caused by it?

[retep998]

With a bit of further testing, the refusing to work outright isn't cargo's fault, but rather rustc's fault, so I'll have to open another issue for that, and it only applies when creating rlibs, not binaries.

As for the spurious assertion in cargo itself... after updating my nightly it appears that #5887 fixed it.

[retep998]

Closing in favor of rust-lang/rust#54297 given the issue in cargo itself was fixed and instead there is now an issue in rustc.