> Users can simply fix their builds to pull down pekko-streams-circe v1.1.0. Noone has reported an issue yet with the couple of affected connectors.
Unfortunately this is a poor metric for gauging whether users are effected or not because due to how pekko-streams work, it's not always clear that the issue is actually coming from pekko-streams-circe i.e. see https://github.com/apache/pekko-http/issues/595 At least to me, if we have critical bugs (such as this one) we should try and release a fixed version as soon as we can. On Thu, Sep 12, 2024 at 4:16 PM PJ Fanning <fannin...@apache.org> wrote: > Users can simply fix their builds to pull down pekko-streams-circe v1.1.0. > Noone has reported an issue yet with the couple of affected connectors. > Since there is an easy workaround and there are a number of releases > that we need to do, I would favour leaving this for now. > > On Thu, 12 Sept 2024 at 15:08, Matthew de Detrich <mdedetr...@apache.org> > wrote: > > > > Hello, > > > > https://github.com/apache/pekko-connectors/pull/796 was just merged and > > it contains a critical fix[1], the criticality here is that > > pekko-streams-circe would > > fail to stream JSON properly for certain sizes/buffers of JSON. > > > > Given this, should we release Pekko Connectors 1.0.3? I would volunteer > as > > RM but I am travelling and hence don't want to take my signing key with > me. > > > > 1: https://github.com/mdedetrich/pekko-streams-circe/pull/93 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > >
