Can't open projects with Nightly package

[sylwiabr]

Discord username

No response

What type of issue is this?

Permanent – Occurring repeatably

Is this issue blocking you from using Enso?

• Yes, I can't use Enso because of this issue.

Is this a regression?

• Yes, previous version of Enso did not have this issue.

What issue are you facing?

When creating a new project or opening existing one with Nightly packages newer then 16.12 error occurs

Expected behaviour

Projects should run

How we can reproduce it?

No response

Screenshots or screencasts

No response

Logs

No response

Enso Version

Nightly 16.12 and newer

Browser or standalone distribution

Standalone distribution (local project)

Browser Version or standalone distribution

standalone

Operating System

MacOS

Operating System Version

No response

Hardware you are using

No response

[hubertp]

Likely caused by 96c5f31

[4e6]

This may be a macOS issue. I have no problems with the latest nightly on Linux.

We had some issues with signing macOS package after the upgrade. Can be related #11914

[hubertp]

True, I can confirm that it works on Linux.

[hubertp]

It seems to be fine on Windows as well

[hubertp]

Fix merged, needs verification after next nightly is out.

[hubertp]

Nightly appears to be still broken. Potentially the problem is in the signing process.

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2025-01-06):

Progress: Still doing some tweaks to NI integration, addressing PR review. Trying to diagnose again jline issue. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11957 task. Continue investigating tickets

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2025-01-07):

Progress: Merged NI integration work. Attempts to make jline initialize at build time, failed. Splitting jline into individual dependencies. Planning session. Fixed deployment of self-hosted runners. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11957 task. Continue investigating tickets

[JaroslavTulach]

I have just tried 2025.1.9.1 .dmg. I believe the different is in JAR manifests. The manifest of jline-native-3.26.3.jar is empty in the .dmg file:

Enso2.app/Contents/Resources/enso/dist/2025.1.1-nightly.2025.1.9.1/component$ unzip -p jline-native-3.26.3.jar META*MANI*
Manifest-Version: 1.0
Created-By: 21.0.2 (GraalVM Community)

while in the sbt buildEngineDistribution it contains a lot of attributes:

$ unzip -p ./built-distribution/enso-engine-0.0.0-dev-macos-aarch64/enso-0.0.0-dev/component/jline-native-3.26.3.jar META*MANI*
Manifest-Version: 1.0
Created-By: Apache Maven Bundle Plugin 5.1.9
Build-Jdk-Spec: 22
Automatic-Module-Name: org.jline.nativ
Bundle-Description: JLine
Bundle-License: https://opensource.org/licenses/BSD-3-Clause
Bundle-ManifestVersion: 2
Bundle-Name: JLine Native Library
Bundle-SymbolicName: org.jline.native
Bundle-Version: 3.26.3
Export-Package: org.jline.nativ;version="3.26.3"
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Tool: Bnd-6.3.1.202206071316

most imporantly the Automatic-Module-Name: org.jline.nativ is missing. That would probably be the cause of

as well. If the Automatic-Module-Name: org.jline attribute was missing, then obviously the JVM module system could not find such module.

[hubertp]

Something is really odd. As you can see all the other jline deps are being correctly signed, while jline-native is clearly not.

> ls jlin*
jline.md                                                 jline-reader-3.26.3.jar:com.apple.cs.CodeSignature         jline-terminal-jna-3.26.3.jar
jline-native-3.26.3.jar                                  jline-terminal-3.26.3.jar                                  jline-terminal-jna-3.26.3.jar:com.apple.cs.CodeDirectory
jline-reader-3.26.3.jar                                  jline-terminal-3.26.3.jar:com.apple.cs.CodeDirectory       jline-terminal-jna-3.26.3.jar:com.apple.cs.CodeEntitlements
jline-reader-3.26.3.jar:com.apple.cs.CodeDirectory       jline-terminal-3.26.3.jar:com.apple.cs.CodeEntitlements    jline-terminal-jna-3.26.3.jar:com.apple.cs.CodeRequirements
jline-reader-3.26.3.jar:com.apple.cs.CodeEntitlements    jline-terminal-3.26.3.jar:com.apple.cs.CodeRequirements    jline-terminal-jna-3.26.3.jar:com.apple.cs.CodeRequirements-1
jline-reader-3.26.3.jar:com.apple.cs.CodeRequirements    jline-terminal-3.26.3.jar:com.apple.cs.CodeRequirements-1  jline-terminal-jna-3.26.3.jar:com.apple.cs.CodeSignature
jline-reader-3.26.3.jar:com.apple.cs.CodeRequirements-1  jline-terminal-3.26.3.jar:com.apple.cs.CodeSignature       jlink

[hubertp]

duh https://github.com/enso-org/enso/blob/develop/app/ide-desktop/client/tasks/signArchivesMacOs.ts#L225

GitHub

enso/app/ide-desktop/client/tasks/signArchivesMacOs.ts at develop · enso-org/enso

Enso Analytics is a self-service data prep and analysis platform designed for data teams. - enso-org/enso

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2025-01-08):

Progress: Prepared PR that cleans up jline dependencies. Removed scala-compiler dependency that was pretty heavy. Not sure if that will address the issue as I cannot reproduce locally. Debugging lack of widgets on startup. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11957 task. Continue investigating tickets

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2025-01-09):

Progress: More testing of PR. Continued debugging widgets issue. Debugging issues with NI. It should be finished by 2025-01-09.

Next Day: Next day I will be working on the #11957 task. Continue investigating tickets