You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This potential bug doesn't affect pre-built images. It only affects users who want to call the script install_julia.sh to install the latest version of Julia in the Docker image.
If a user doesn't specify the environment variable JULIA_VERSION, the current script install_julia.sh will always install Julia v1.9.4, even though the latest stable version of Julia is 1.10.1 now.
Changing this line latest_version <- sort(versions[is_stable], decreasing = TRUE)[1]
to latest_version <- as.character(sort(numeric_version(versions[is_stable]), decreasing = TRUE)[1])
should fix the issue.
The text was updated successfully, but these errors were encountered:
+1 for "juliaup"-ify the script. My use case: I teach courses in a biostatistics department in different languages: R, Python, and Julia. It'll be nice to have an image with the full JUPYTER (Julia+Python+R) stack. I used to build from the math-server-docker, but that's CentOS-based and the build process is unbearably long.
This potential bug doesn't affect pre-built images. It only affects users who want to call the script
install_julia.sh
to install the latest version of Julia in the Docker image.If a user doesn't specify the environment variable
JULIA_VERSION
, the current scriptinstall_julia.sh
will always install Julia v1.9.4, even though the latest stable version of Julia is 1.10.1 now.Changing this line
latest_version <- sort(versions[is_stable], decreasing = TRUE)[1]
to
latest_version <- as.character(sort(numeric_version(versions[is_stable]), decreasing = TRUE)[1])
should fix the issue.
The text was updated successfully, but these errors were encountered: