roekatz

@WellyHong I wasn't able to reproduce this locally by configuring wrong `entries.url`: 1. The opal-client shuts down instead of retrying, so memory never accumulates. 2. I get a `TimeoutError()` rather...

@WellyHong Great! that helped me reproduce the issue. The source of the memory leak is in our `FASTAPI Websocket RPC` library . The client's `connect` method is retried indefinitely while...

Thanks @maxrabin !

@emmanuel-ferdman Thanks! :)

Hi @kostiapl, sorry for the late respond. Have you had the chance to try using `csi-s3`? I'm not sure adding support for backup stores for offline mode (other than filesystem)...

There should be no issues with broadcasting updates across instances in recent OPAL releases. @asafc The fixes introduced by that PR are of a more nuanced nature. @yadunandan004 Yes I...

Closing because old, possibly fixed with: https://github.com/permitio/opal/issues/274

Closed by #349

This is not flaky anymore

Hi @dariosky, I was involved in this fix on our fork `https://github.com/permitio/broadcaster`. I don't believe automatically reconnecting is a good idea: when connection is loss messages could be missed, therefor...