-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
I created a demo project that shows the issue: https://github.com/ChrisIgel/helm-demo
When running the Main everything is fine. Also when the project is built as a JAR and then run, everything works as expected. Only when using the Quarkus dev mode the first Helm command will hang (all subsequent calls work just fine). This can be resolved by pressing a key (i.e. enter or space) a couple of times in the console.
Any idea what the problem might be?
I'm using Windows and I'm getting the following output:
2025-12-02 16:51:19,879 INFO [org.acme.HelmService] (Quarkus Main Thread) Get instance: com.marcnuri.helm.jni.windows.amd64.WindowsAmd64NativeLibrary@782dc800
2025-12-02 16:51:19,879 INFO [org.acme.HelmService] (Quarkus Main Thread) Load instance
2025-12-02 16:51:20,644 INFO [org.acme.HelmService] (Quarkus Main Thread) Load instance: Proxy interface to Native Library <C:\Users\chris\AppData\Local\Temp\helm-java5130737126556138867\helm-windows-4.0-amd64.dll@140711865942016>
2025-12-02 16:51:20,644 INFO [org.acme.HelmService] (Quarkus Main Thread) Version call
### this is where it hangs and I have to press a key a couple of times ###
2025-12-02 16:51:53,003 INFO [org.acme.HelmService] (Quarkus Main Thread) Version call: Result(auto-allocated@0x24b7a877c80 (32 bytes)) {
String out@0x0=v3.19.2
String err@0x8=null
String stdOut@0x10=null
String stdErr@0x18=null
}
Metadata
Metadata
Assignees
Labels
No labels