-
Notifications
You must be signed in to change notification settings - Fork 323
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
AppImage cannot be used expanded: tries to download GraalVM #7698
Comments
Likely caused by latest GraalVM upgrade and (now) broken links: Line 637 in 87ce786
Should have more a format similar to |
Actually, looks like locally we download and rename artifacts to fir the old format. But we don't do that when creating the AppImage. We should. |
@mwu-tow agreed to take over as this is very much in the build script/rust domain when we define bundles. |
While looking into #7698 discovered that the `buildGraalDistribution` task would fail to use the old (pre-23.0) GraalVM naming of artifacts. This has changed since #7176. The fix does not attempt to fix a problem of packaged GraalVM name in `runtime`. That, as the ticket mentiones it, is the role of rust build script that creates the correct bundle.
While looking into #7698 discovered that the `buildGraalDistribution` task would fail to use the old (pre-23.0) GraalVM naming of artifacts. This has changed since #7176. The fix does not attempt to fix a problem of packaged GraalVM name in `runtime`. That, as the ticket mentiones it, is the role of rust build script that creates the correct bundle.
Trying to investigate the behavior behind proxy
I contacted a friend behind a corporate proxy and asked him to use https://github.com/enso-org/enso/releases/tag/2023.2.1-nightly.2023.8.29. He downloaded
AppImage
and tried to use it on his Ubuntu. He doesn't have FUSE installed, so theAppImage
told him to extract itself. After doing so, starting./AppRun
and creating the new project, everything stopped becauseGraalVM runtime [GraalVM 23.0.0 Java 17.0.7] not found.
But the runtime is part of theAppImage
!I'd say the error is in cooperation between
org.enso.runtimeversionmanager.components.RuntimeVersionManager
and the wayAppImage
is built.The text was updated successfully, but these errors were encountered: