Closed gaeljw closed 1 week ago
Since this is very likely to be a zio problem, could you please open the issue at https://github.com/zio/zio ?
Thanks for taking the time to report this. This does not ring a bell and I don't immediately have a change in 2.1.8 that I suspect (based on https://github.com/zio/zio/releases/tag/v2.1.8). I tried to reproduce it (using zio test instead of scalatest), but the test succeeds. That is with zio version 2.1.9
Could you perhaps enable logging for org.apache.kafka (using logback) and see if there's anything of interest there that could explain anything?
And, taking a wild guess here, are you using ARM perhaps? There's a note in the 2.1.8 release notes about that.
Since this is very likely to be a zio problem, could you please open the issue at https://github.com/zio/zio ?
@erikvanoosten Sure, discussion moved to https://github.com/zio/zio/issues/9222 then.
For the record, it's related to https://github.com/zio/zio/issues/9208.
Need to explicitly set the zio-streams
version to the same as zio
to workaround it.
Wow, I would not have guessed that 😅 Good to hear your issue is fixed
(This might be an issue with ZIO core itself but I'm opening it here as it's visible through zio-kafka in my case)
When upgrading from
zio
2.1.7 to 2.1.8 (or 2.1.9), the following code stops working.Code
Versions
Results
With
zio
2.1.8 (or 2.1.9):Future timed out after [30 seconds] java.util.concurrent.TimeoutException: Future timed out after [30 seconds]
(on theAwait.result
).With
zio
2.1.7: the test succeeds (in about 5 seconds on my laptop, all included).