Zanie Blue
Zanie Blue
I don't think this is in scope for us, happy to support a Debian package maintainer if anything is needed — just reach out.
> Sounds like as of Dec 1st, most of the rust dependencies were either not packaged or out of date. https://lists.debian.org/debian-python/2024/12/msg00000.html We're pretty on top of using the latest versions...
I'm interested!
I'm also interested in _always_ writing to a log file in a temporary directory unless it's disabled? Like `UV_LOG_DIR`? I'm not sure what this would look like in practice.
Hi! I think this makes sense, though I have a few comments: > If log path not set it should default to logs directory in the root folder Just remember...
My motivation is to not need to enable logging and re-run a command to see failures. I want to be able to say "See for more logs" on failure —...
It's fine to add content to the existing snapshots. cc @Gankra for general awareness about output changes
If someone wants to put some effort into getting an ARM build working I'm all for it. I think we could start with something low impact like the #8269 build...
@kalradivyanshu I added a runner called `github-windows-11-aarch64-4` to the org. I think the idea would basically be to copy the following job with the aarch64 runner and call it `build-binary-windows-aarch64`...
That sounds correct to me, yep!