Nadav Wiener

Revisiting this one year later, I can provide two references where this is addressed: When http4s fails to parse something, their [ParseFailure](https://github.com/http4s/http4s/blob/v0.17.0-M2/core/src/main/scala/org/http4s/MessageFailure.scala#L38) type allows providing both a detailed message, and...

I just installed Zulu OpenJDK 11.0.7 JRE into this base image: ``` ADD https://cdn.azul.com/zulu/bin/zulu11.39.15-ca-jre11.0.7-linux_x64.tar.gz /opt/ ENV JAVA_HOME /opt/zulu11.39.15-ca-jre11.0.7-linux_x64 ``` `java --version` gains me a fairly similar crash: ``` openjdk 11.0.7...

Went over some closed tickets. @frol indicates that `ldd` output can be misleading here, and suggests prefacing with `LD_TRACE_LOADED_OBJECTS=1` instead. ``` / # LD_TRACE_LOADED_OBJECTS=1 $JAVA_HOME/bin/java linux-vdso.so.1 (0x00007ffe48df2000) libz.so.1 => /lib/libz.so.1...

Same behavior—zlib still leads to musl being loaded: Ran it with `LD_DEBUG=libs` to see library loads as they happen. Output for `LD_DEBUG=libs /usr/glibc-compat/lib64/ld-linux-x86-64.so.2 $JAVA_HOME/bin/java --version` and `LD_DEBUG=libs $JAVA_HOME/bin/java --version` is...

We've been able to get the JVM not to crash by lifting a prebuilt glibc-based zlib from another distro (forgot where I saw this, perhaps on a different ticket in...

I nominate @kthy for best use of "baleeted" in a GitHub issue

The problem is with the [`multiStage`](https://github.com/sbt/sbt-native-packager/blob/master/src/main/scala/com/typesafe/sbt/packager/docker/DockerSupport.scala#L16-L17) snippet. It checks for `17.05`, then [uses `makeCopyFrom`](https://github.com/sbt/sbt-native-packager/blob/master/src/main/scala/com/typesafe/sbt/packager/docker/DockerPlugin.scala#L171), which in turn [uses `COPY --from=... --chown=...](https://github.com/sbt/sbt-native-packager/blob/master/src/main/scala/com/typesafe/sbt/packager/docker/DockerPlugin.scala#L341). `COPY --from=... --chown=...` has the same version availability as...

+1 for doing this. I realize this isn't the policy for json4s, but users generally expect backward binary compatibility between minor releases, and breakage only between major releases.

@ekrich I agree that using pthreads makes lots of sense for Scala Native, and that supporting real time priorities can be a appealing (with the same disclaimer regarding alternative concurrency...

The need for a concurrency-friendly memory model only arrives when we use multiple cores. If we were to implement pthreads-based `java.util.Thread` and `Monitor`, with the additional step of setting thread...