Denis Cornehl

I created a draft PR to implement this feature, following the pattern from Taskfile (parallel execution of dependencies, parallel task execution when given multiple tasks on the commandline). More work...

This is totally possible to do, I would totally accept a PR solving this. Since https://github.com/rust-lang/docs.rs/issues/1011 and https://github.com/rust-lang/docs.rs/pull/2533 we see the crates when we started building them, but not yet...

Small update here: since we cache in the CDN now, this tracking would either have to be JS, or based on the CDN logs.

For now I don't see us adding a third party cargo extension to the compiler toolchain we use to build docs. Network access won't be allowed for security reasons. From...

Could you relaborate what's missing for you? I'm aware that the situation could be better, but I would like to understand what would help you more. What we currently have...

I don't have much time to dig into how your package and `inari` interact, but here some points where you can start looking: For these kind of errors it's always...

from what I see, this is either #1957 or #93

the actual error is: > error: failed to parse manifest at `/home/cratesfyi/workspace-builder/builds/protoc-plugin-by-closure-0.1.3/source Cargo.toml` > Caused by: > `artifact = …` requires `-Z bindeps` (protoc-plugin-bin) ( I need to check why...

short research result: for these pre-build errors we just render the error variant we get, in this case `rustwide::CommandError`, which only contains the status code. We additionally need to collect...

https://github.com/rust-lang/docs.rs/pull/2635 should help with this