search

enso-org / enso

Hybrid visual and textual functional programming.
https://enso.org
Apache License 2.0
7.32k stars 320 forks source link

Use builtin edition when project's edition cannot be found #8948

Closed hubertp closed 5 months ago

hubertp commented 5 months ago

When we create a new Enso project, package.yaml includes the current engine version with which it was created. This is problematic when sharing projects and after upgrades.

When one upgrades Enso and tries to use an old project with an engine that is now missing it will fail completely to boot the project. Instead, we could send a warning to GUI of an automatic upgrade and still attempt to use the builtin version of the engine.

4e6 commented 5 months ago

The current logic is to ignore the edition field and start the project using the packaged language server. It was implemented in #7868

hubertp commented 5 months ago

Tried with different subprojects. I can't reproduce anymore. Will reopen if it occurs again.