Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pixi global can't deal with trampolines that don't have a corresponding `json #2537

Closed
2 tasks done
Hofer-Julian opened this issue Nov 21, 2024 · 0 comments · Fixed by #2576
Closed
2 tasks done

pixi global can't deal with trampolines that don't have a corresponding `json #2537

Hofer-Julian opened this issue Nov 21, 2024 · 0 comments · Fixed by #2576
Labels
area:global Related to pixi global

Comments

@Hofer-Julian
Copy link
Contributor

Checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi global install nushell
cd ~/.pixi/bin
cp nu nu2
pixi global update
  × failed to read from file `/var/home/julian/.pixi/bin/trampoline_configuration/nu2.json`
  ╰─▶ No such file or directory (os error 2)

Issue description

pixi global can't deal with trampolines that don't have a corresponding json file.
It simply crashes.

Expected behavior

It should remove the trampoline binary without corresponding json file

@Hofer-Julian Hofer-Julian added the area:global Related to pixi global label Nov 21, 2024
Hofer-Julian added a commit to Hofer-Julian/pixi that referenced this issue Nov 27, 2024
jjjermiah pushed a commit to jjjermiah/pixi that referenced this issue Nov 30, 2024
Fixes prefix-dev#2537

- Fix behaviour
- Add test
- Rename `GlobalBin` to `GlobalExecutable`
- Add logging messages
- Remove `test_sync_clean_up_broken_exec` -> we only clean up invalid
trampoline-configuration pairs now
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:global Related to pixi global
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant