pixi install fails on macOS

[jarrah42]

I did the following:

% pixi run copier copy https://github.com/nova-sdk/nova-application-template.git project_folder
🎤 What kind of application are you creating?
   NDIP Tool
🎤 What is your project name?
   foo
🎤 What is your Python package name (use Python naming conventions, use dots to
   foo
🎤 Which category will your tool belong to?
   Generic
...
% cd project_folder
% pixi install
 WARN osx-arm64 (Apple Silicon) is not supported by the pixi.toml, falling back to osx-64 (emulated with Rosetta)
Error:   × failed to map conda packages to their PyPI equivalents. This mapping is
  │ required when using PyPI dependencies alongside conda packages.
  ├─▶ failed to fetch conda-pypi mapping from remote source
  ├─▶ error sending request for url (https://conda-mapping.prefix.dev/hash-
  │   v0/6eed58051c2e12b804d53ceff5994a350c61baf117ec83f5f10c953a3f311451)
  ├─▶ client error (Connect)
  ╰─▶ invalid peer certificate: UnknownIssuer

[bvacaliuc]

Hi Greg - I came across a similar issue today in my own development and a google search brought your issue up for me.

In my case, I solved it by transferring all [tool.pixi.pypi-dependencies] to [tool.pixi.dependencies]. The pixi docs for conda ^ pypi suggest preferring to use conda dependencies over pypi ones.

issue3-changes-transcript.txt
issue3-changes.patch

I followed your steps, reproduced it on my system, then made edits to your generated project as per the attached patch. It solves your pixi install problem. It is not exactly a solution for nova yet because it comments out the line:

+[tool.pixi.pypi-dependencies]
+#foo = { path = ".", editable = true }

Any pypi dependency can lead to this issue on osx at the moment. I think taking steps to avoid them in the project template is a good move. I am also (personally) opposed to the 'pip: -e .' idiom, so perhaps the way forward with pixi/uv is described in uv #editable-dependencies?

[evilkermit]

FYI, the underlying issue here is the firewall. The best way, in my opinion, to permanently fix this is to configure Pixi to use the system's native TLS certificates. You can do so by creating $HOME/.pixi/config.toml with:

tls-root-certs = "native"

Full reference on what this is doing is available here: https://pixi.prefix.dev/v0.63.2/reference/pixi_configuration/