Vladimir Kamarzin

Any updates? I see not much progress in PRs review process unfortunately.

We've got exactly this situation with AWS MSK. This happens when aiokafka is able to connect to a broker, but then some timeout occurs in `AioKafkaConnection.connect()`, which triggers `Unclosed AIOKafkaConnection`...

Guys could you explain why this change was introduced? I'm often getting an errors while making transactions. I'm on golos blockchain and I'm using a forked version of steem-python. Here...

@sneak I think reasonable default is use last_irreversible_block as a reference. This will prevent transactions loosing at chain forks.

OK I did not included ark recipe in my recipe like ``` include_recipe 'ark' ``` Probably README should mention this? Now it's not.

Just migrate to Github Actions, it's already used for python-graphenelib.

Here is our example to cache `/usr/share/miniconda/envs`. **Updated** ```yml - uses: conda-incubator/setup-miniconda@v2 with: activate-environment: "xxx" auto-activate-base: false use-only-tar-bz2: true # IMPORTANT: This needs to be set for caching to work...

@lminer hmm, make sure that you have `activate-environment: myenv` in `conda-incubator/setup-miniconda@v2` step.

@lminer ok, I was trying to fix some issues after recent 2.1.0 release of `setup-miniconda` action. I've updated the example above. Note that there is no `rm -rf` step anymore...

@ods I've checked the code in #810, the fix is a bit different from what I've did in https://github.com/bitphage/aiokafka/commit/b1904e22c17f5593ad98649250d2a183dab29a8c Specifically, in #810 in `aiokafka/conn.py` ```python async def connect(self): # skipped...