Replies: 4 comments 1 reply
-
I am behind a corporate network otherwise I would have posted the trace output of the commands. One other tidbit I can add is that we use Artifactory as a remote proxy for conda-forge due to firewalls blocking access to conda-forge on conda.anaconda.org and prefix.dev's hosted mirrors too. |
Beta Was this translation helpful? Give feedback.
-
Can you see on which URL it gives the 400? I assume on the One difference is that we might use |
Beta Was this translation helpful? Give feedback.
-
Was there any big difference between after 0.45? If we are using 0.45 from conda-forge we do not seem to hit the issue. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately I did not get anywhere when I got home. I tried installing Pixi from conda-forge on my personal laptop and I did not hit the same issue. I am wondering if there is something with how Pixi is talking to Artifactory with TLS in the new versions built for conda-forge. Troubleshooting Pixi HTTP 400 error on Mac OS X when installed from conda-forgeConda version information
Install Pixi into a new environment
Create new Pixi project
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Opening a discussion before opening an issue.
We are currently getting Pixi approved for use internally. In the meantime, we are installing Pixi from conda-forge. We have not seen this issue on Linux or Windows, but on Mac we get a HTTP 400 whenever we create or update the lock file.
We tried different versions of Pixi from conda-forge and had to downgrade all the way to 0.45.0 before it started to work again.
I tried installing Pixi in the Minforge base environment and also in an environment all by itself.
When I run
pixi install -vvvv
orpixi lock -vvvv
for pixi>=0.46.0 on Mac when installed using conda from conda-forge I will see the HTTP 400 when it tries to solve requirements for an environment. The trace message is referencingrattler_repodata_gateway::fetch::with_cache
when trying to fetch repodata.json.We are not seeing this issue on Linux or Windows.
We are also not seeing this for Mac IF we get Pixi straight from the GitHub asset section of the Pixi release.
Beta Was this translation helpful? Give feedback.
All reactions