David M. Lloyd
David M. Lloyd
Yeah I think we'll always need this switch in 24+ (alternatively, we could try not clearing thread locals). Note that once we start moving to a modular run time (#43749)...
Oops, that's a different problem (looks like a real bug).
https://github.com/jbossas/jboss-threads/issues/237
> Thanks. Does that mean this will only be fixed once quarkus picks up a new jboss threads version (provided the `--add-opens` is being added on the quarkus side)? Correct.
I'll link the component upgrade PR to this issue, once it comes through. It seems there are ongoing problems with staging things to Maven Central but hopefully it will be...
I think the manifest entry is OK.
> Usually Windows FS is case-insensitive (i.e. you cannot have `podman.exe` and `podman.EXE` in the same folder). I think this is a special case with podman version command: > >...
> Currently, `ProcessUtil.pathOfCommand(Path.of("docker"))` will return `C:\Program Files\Docker\Docker\resources\bin\docker.EXE` instead of `C:\Program Files\Docker\Docker\resources\bin\docker.exe`. > > This PR will fix a recent bug in latest Quarkus with podman detection on Windows: > >...
> * Provides explicit Sisu component registration via META-INF/sisu/javax.inject.Named > to replace the deprecated Sisu index in Maven 4 Question: if this mechanism is deprecated, what replaces it?
Quick peek link: https://github.com/dmlloyd/wildfly-proposals/blob/threadpool/thread-pool/WFCORE-3397_New%20Thread%20Pool.adoc