Repository navigation
Conversation
…k it install-shim resolved Julia to the versioned juliaup path (julia-X.Y.Z+0.../bin/julia), which juliaup deletes on upgrade, leaving the shim pointing at a missing binary. Pin ~/.juliaup/bin/julialauncher instead when the resolved binary is juliaup-managed, and give a clear reinstall hint when JULIA_REAL_BIN no longer exists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
make julia-daemon SHIM=1writes~/.local/bin/juliawithJULIA_REAL_BINset to the resolved, versioned juliaup binary (e.g.~/.julia/juliaup/julia-1.13.1+0.x64.linux.gnu/bin/julia). When juliaup upgrades the channel it deletes that directory, so everyjuliacall through the shim fails with the misleadingJulia not found; run 'make install julia' first.Fix
install_shim: if the resolved binary is juliaup-managed (*/juliaup/julia-*/bin/julia) and~/.juliaup/bin/julialauncherexists, pin the launcher instead. It follows the default channel across upgrades.require_julia: whenJULIA_REAL_BINis set but missing, say so and print the reinstall command.Test
Upgraded 1.13.1 → 1.13.2, then reinstalled with
JULIA_REAL_BIN=$HOME/.juliaup/bin/julia make julia-daemon SHIM=1:julia -e ...(fallback path) → 1.13.2julia --project=. -e ...twice → same daemon PID both calls (3.7s cold, 1.2s warm)status/stopwork. The launcher execs julia, so the PID/cmdline identity check still matches.🤖 Generated with Claude Code