Enso Engine bundle doesn't work without downloading

[JaroslavTulach]

I've just downloaded latest nightly Enso engine bundle for Linux. When I try to use it:

enso$ ./bin/enso repl
Do you want to install the missing runtime? [Y/n]

it doesn't work and asks for download of something. That's wrong. The bundle shall work out of the box.

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2023-09-26):

Progress: Was trying to fix the failing tests on CI. Introduced a new fake release. Tried to create a separate PR. Tried a clean build. Noticed that the clean step is not always triggered even if the appropriate tag exists. But even if the clean build is triggered, the CI fails anyway. It should be finished by 2023-10-02.

Next Day: Next day I will be working on the #7871 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2023-09-27):

Progress: Started working on the issue. Built the IDE from develop and was able to reproduce the issue when the engine downloads an unknown release together with the runtime, even if the appropriate runtime is included in the bundle. Started to look into why the bundled runtime is not added to the search path. It should be finished by 2023-10-02.

Next Day: Next day I will be working on the #7871 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2023-09-28):

Progress: Temporarily switched to fixing the failing on CI PR. Found that the CI overrides the enso version, causing the new tests to fail. Updated the tests to override the enso version to a predefined one. Switched back to debugging the project manager bundle It should be finished by 2023-10-02.

Next Day: Next day I will be working on the #7871 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2023-09-29):

Progress: Continue working on the issue. Confirmed that the bundle is built correctly and the packaged GraalVM is present on the search path. Found that the issue is because the GraalVM directory does not match the expected pattern. Discovered that the logic that creates the bundle is duplicated in SBT and Rust run script. The SBT one is not used. Both produce incorrect GraalVM directory name. It should be finished by 2023-10-02.

Next Day: Next day I will be working on the #7871 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2023-10-02):

Progress: Continue working on the issue. Added a graalvm version to the build config. Update the run build script logic to create a bundle runtime directory based on the config values. Tested with IDE. Created the PR It should be finished by 2023-10-02.

Next Day: Next day I will be working on the #7871 task. Continue working on the task