Eric Dallo

@jeanbisutti ``` native-image 23.0.1 2024-10-15 GraalVM Runtime Environment GraalVM CE 23.0.1+11.1 (build 23.0.1+11-jvmci-b01) Substrate VM GraalVM CE 23.0.1+11.1 (build 23.0.1+11, serial gc) ``` @jack-berg I reproed that using the log...

It's still a improvement for default, I suggest merge it so users don't need to spend debugging I like I did

What this action is supposed to do? could you elaborate the problem you are trying to solve with this action?

clojure-lsp doesn support win aarch64 yet, but clients like calva should use the standalone jar or the `clojure-lsp.bat` for win aarch64 instead of downloading the win x64.

Can anyone provide a sample flutter project where that happens so I can try? I can't repro yet

I think I foudn the issue, can you try again with latest?

Hum @DavidAlphaFox I wonder why we don't have this problem on [clojure-lsp](https://github.com/clojure-lsp/clojure-lsp/blob/6a9def7d477bbd36bf508b79494071c91a21b6b5/lib/src/clojure_lsp/classpath.clj#L69) which has the exact same logic 🤔

@jkxyz I believe this is a clojure-lsp issue as I never dedicated time to make it remote filesystem aware, it's pretty coupled with local files unfortunatelly

one way to debug that is get logs between client server, more info [here](https://clojure-lsp.io/troubleshooting/#client-server-log)

The problem happens because we use java URI [here](https://github.com/clojure-lsp/clojure-lsp/blob/b215bccf8f41240dd3a5d127af9120f0015f39fc/lib/src/clojure_lsp/shared.clj#L212) for a lot of features and it seems java URI doesn't support non-ascii chars. Not sure the best way to fix...