Georg

Hi, is this related? ``` [ 133s] tests/test_asyncio/test_pubsub.py::TestPubSubSubcommands::test_pubsub_numsub[pool-python-parser] FAILED [ 134s] =================================== FAILURES =================================== [ 134s] _________ TestPubSubSubcommands.test_pubsub_numsub[pool-python-parser] _________ [ 134s] [ 134s] self = [ 134s] r = Redis...

@stamfest I think you should just publish it as a fork at this point. These are some neat additions.

Easiest is to use the default multicast discovery mechanism, as described [here](https://www.keycloak.org/server/caching). If you want to set other options, like fixed addresses, you unfortunately need to write a custom Infinispan...

Repacking a binary release does not make sense. The software shall be built from source as part of the build process. Since this software requires Real-ESRGAN, that should be packaged...

> This is regarding to the PKGBUILD, yes? Yes. > I generally agree, but having *-bin of packages make installing much easier, Interesting, I didn't know that was a thing...

Thanks for your reply! Maybe something changed in Docker's authorization API? The log output I pasted already comes from what the Docker daemon prints to the system journal.

Thank you for elaborating, @rhusar. Does that mean it is recommended to use 1.3.11 or to build 1.4.x on ones own? As the binary installation documentation I linked does not...

Sorry, I don't know what apachelounge is and do not use Windows.

openSUSE, but how is it related? I can run either version just fine, it is just not clear what the recommended route is.

Sorry for the confusion. I wasn't complaining or anything - I just got confused at the manual section "Download" and "Quick start" instructing you to download and extract release binaries...