Not Starting Up Properly Probably Due to Unix Domain Socket Length Limitations

[tthornton3-chwy]

Good evening! I and a couple other people on the team can say now that after upgrading to the latest VSCode Insiders / vscode-java standard/preview versions, the extension is not starting up successfully.
The "spinning" wheel keeps spinning indefinitely, and if you go to "Show Build Status" you get an absolutely empty window with no logs/status, at any point.
There are no interesting errors in any of the typical "Output" windows, for anything java. However, a Java: Open all Log Files gives at least this:

!SESSION 2023-10-30 16:02:54.536 -----------------------------------------------
eclipse.buildId=unknown
java.version=17.0.3
java.vendor=Eclipse Adoptium
BootLoader constants: OS=macosx, ARCH=aarch64, WS=cocoa, NL=en_US
Framework arguments:  --pipe=/var/folders/c4/f8v01p_s2sn9_hrx6y18dlxr0000gq/T/vscode-b4e4949e2fde772119c33ebd3ad375f0e8b742abf2.sock
Command-line arguments:  -data /Users/[redacted]/Library/Application Support/Code - Insiders/User/workspaceStorage/e0a072670fac3ceed984d299690f5fdc/redhat.java/jdt_ws --pipe=/var/folders/c4/f8v01p_s2sn9_hrx6y18dlxr0000gq/T/vscode-b4e4949e2fde772119c33ebd3ad375f0e8b742abf2.sock

!ENTRY org.eclipse.jdt.ls.core 1 0 2023-10-30 16:02:56.397
!MESSAGE class org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin is started

!ENTRY org.eclipse.jdt.ls.core 4 0 2023-10-30 16:02:56.474
!MESSAGE Unix domain path too long
!STACK 0
java.net.SocketException: Unix domain path too long
	at java.base/sun.nio.ch.UnixDomainSockets.connect0(Native Method)
	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:148)
	at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:144)
	at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:851)
	at org.eclipse.jdt.ls.core.internal.ConnectionStreamFactory$PipeStreamProvider.initializeNamedPipe(ConnectionStreamFactory.java:117)
	at org.eclipse.jdt.ls.core.internal.ConnectionStreamFactory$PipeStreamProvider.<init>(ConnectionStreamFactory.java:89)
	at org.eclipse.jdt.ls.core.internal.ConnectionStreamFactory.createProvider(ConnectionStreamFactory.java:269)
	at org.eclipse.jdt.ls.core.internal.ConnectionStreamFactory.getSelectedStream(ConnectionStreamFactory.java:257)
	at org.eclipse.jdt.ls.core.internal.ConnectionStreamFactory.getInputStream(ConnectionStreamFactory.java:275)
	at org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin.startConnection(JavaLanguageServerPlugin.java:344)
	at org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin.startLanguageServer(JavaLanguageServerPlugin.java:441)
	at org.eclipse.jdt.ls.core.internal.LanguageServerApplication.start(LanguageServerApplication.java:54)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:651)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:588)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1459)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1432)

This makes me think like maybe something was changed where the socket lives, and when running Insiders the path just gets too big / longer than 100~ characters?
This would explain why i'm not seeing any log/error messages in "Show Build Status", since we aren't able to actually connect to the socket!

Nothing was changed between 1.23.0 and 1.24.0 over here that would make any sense, so I'm wondering if it's a VS Code Insiders issue with its temp path logic?

Environment

• Operating System: MacOS 13.5 on Silicon
• JDK version: My java.import.gradle.java.home and java.jdt.ls.java.home are at: 17.0.3-tem but getting rid of these doesn't make this go away/do anything different.
• Visual Studio Code version: 1.84.0-insider (No updates at the time of posting)
• Java extension version: v1.24.0 and the preview one too!

Steps To Reproduce

1. Have a Mac on Silicon
2. Have any Java project open in VS Code Insiders w/ latest Language Server extension
3. See the spinny icon spin away, and see the log above!

Current Result

Plugin does not initialize properly, with the error above, and the spinning icon continue to spin indefinitely.

Expected Result

App initalizes properly.

Additional Informations

[snjeza]

The related issue - eclipse-jdtls/eclipse.jdt.ls#2932

[tthornton3-chwy]

Noice! If this is a duplicate I'm happy to close, or if it'll be good to capture it here i'm happy it staying too. Either way i've subscribed to the above, and I will happily test if there's a possible fix!

Btw: try setting "java.transport":"stdio" in your settings. did at least semi-temporarily fix things for me, until we can try again with the new transport method!