Arnout Engelen

Some findings: * I'm still seeing this behavior with Scala 3.4.1-RC1-bin-20240208-7bcfce2-NIGHTLY * It seems to sometimes think (some code related to) `ResponseEntity` is defined in `ParserOutput` for some reason? *...

The `HttpMessage.scala` reference is also somehow related to ResponseEntity. I've been prodding at this with a simplified build in a throwaway branch at https://github.com/raboof/incubator-pekko-http/tree/reproduce-tasty

Looks like this should be fixed in 3.3.5 with https://github.com/scala/scala3/issues/21154 possibly causing what we've seen in the 1.1.0 release at https://arnout.engelen.eu/reproducible-builds-diffoscope-output-pekko-http-core_3-1.1.0.jar/

> Pekko Http built with Pekko Core 1.1.x will still work if you link against Pekko Core 1.0.x at runtime, I have already tested this I think we should *either*...

> So you mean we should do release a whole, eg 2024.04 release？ I personally don't think updating a dependency minor version should require an update of the project major...

> In practice, the mima filters show very very diffs between Pekko 1.0 and Pekko 1.1. I'm not sure if you meant 'very many' or 'very few', but if we...

> there may have been some merit in officially dropping Pekko 1.0.x support I think thats a step too far. I guess at some point we should specify what we...

https://www.rfc-editor.org/rfc/rfc9110.html#field.accept-charset even mentions `Accept-Charset` was deprecated because of the near-ubiquity of UTF-8, and doesn't seem to put any requirements on the server to honour the charset (it merely 'indicates preferences')...

In fact this looks more like https://github.com/lampepfl/dotty/issues/17330 which AFAIK should be fixed in Scala 3.4.0

dynamodb was failing with `[error] warnings found and -Werror specified`, re-running those