Timing-related CI failures on Python 3.11, 3.13, 3.14

[amotl]

About

We just wanted to report that we discovered a downstream CI pipeline failing on Python 3.14. We did not investigate closer yet, but it is likely async-kinesis could be the origin of the problem, or how we are using it, due to a timing issue.

Problem

self = <kinesis.producer.Producer object at 0x7fca72a9ae90>

    async def get_stream_description(self):
    
        try:
            return (await self.client.describe_stream(**self.address))["StreamDescription"]
        except ClientError as err:
            code = err.response["Error"]["Code"]
            if code == "ResourceNotFoundException":
>               raise exceptions.StreamDoesNotExist("Stream '{}' does not exist".format(self.stream_name)) from None
E               kinesis.exceptions.StreamDoesNotExist: Stream 'testdrive' does not exist

/opt/hostedtoolcache/Python/3.14.2/x64/lib/python3.14/site-packages/kinesis/base.py:136: StreamDoesNotExist

References

• CI: Use more Python 3.14 (next) crate/cratedb-toolkit#592 (CI failure)

[hampsterx]

hi @amotl should be good now with 2.2.1 cheers~

[amotl]

Hi. Thank you for the quick turnaround. I re-ran the CI workflow, it is indeed using async-kinesis 2.2.1 now, but still fails on the same occasion. Can you re-open the ticket until we can discover the problem?

[hampsterx]

@amotl try again now with 2.2.2 mbad

[amotl]

Hi and thanks. async-kinesis==2.2.2 is being used well, but the outcome on our CI is still the same:

FAILED tests/io/kinesis/test_cli.py::test_kinesis_dms_stream_universal - 
kinesis.exceptions.StreamDoesNotExist: Stream 'testdrive' does not exist

Maybe it is on us how we are using async-kinesis? Sorry that I currently can only provide this signal, and that I wasn't able to conduct any other investigations yet. However, because everything works well on all previous versions of Python, and because only this single test slot fails, I thought it would be a good idea to report this here. However, maybe something else is the real culprit, timing wise?

[hampsterx]

third times the charm, will see. try 2.2.3 thnx

[amotl]

Same thing, now raised slightly different, but roughly at the same spot, using async-kinesis==2.2.3.

ConnectionError: Kinesis client has exceeded 5 connection attempts

-- PR run #21924343545