Bas Zalmstra
Bas Zalmstra
@wolfv Are you still interested in this PR? Should we upstream the changes?
Those files only exist for backwards compatibility right? All installers support the newer files for years. Why not just drop them?
It disnt work with the generic?
I can confirm that only with "Command Prompt" I get this error: ``` error: unexpected argument '[https://prefix.dev/conda-forge]}' found Usage: pixi config set [OPTIONS] [VALUE] For more information, try '--help'. ```...
It took some time but we just released the new build protocol. We are maintaining a rolling distribution of the build backends on the `pixi-build-backends` channel and a stable one...
I can no longer reproduce this either on Windows or on Linux (WSL). I assume this was fixed upstream. Closing.
is this using amazon aws? Does it retry? are you running index jobs concurrently?
Does Ceph support preconditions? Its a bit unclear because the error also doesnt include a message.
Just to give some context, the changes in rattler_index now first query the s3 storage to read the current etag of the files. Then it goes on with indexing all...
- Should we just store an array of byte offsets? - Should we only store whether the file should be executable? I dont think any other missions matter right? -...