Skip to content

Conversation

jk-ozlabs
Copy link
Member

Current CI is failing in what looks to be a anyio/trio incompatibility.

Bump trio, and upload meson test logs as an artifact.

The version of anyio that currently gets pulled in through asyncdbus
is incompatible with trio:

      File "/home/jk/devel/mctp/mctp/venv/lib/python3.11/site-packages/anyio/_backends/_trio.py", line 141, in cancel
        self.__original.cancel(reason)
      File "/home/jk/devel/mctp/mctp/venv/lib/python3.11/site-packages/trio/_core/_ki.py", line 183, in wrapper
        return fn(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^
    TypeError: CancelScope.cancel() takes 1 positional argument but 2 were given

With the breaking change at
agronholm/anyio@b2c933cd .

Bump trio to 0.31 to support cancel reasons.

Signed-off-by: Jeremy Kerr <[email protected]>
@mkj
Copy link
Member

mkj commented Oct 14, 2025

Should transitive dependencies like anyio also be added to requirements.txt?

meson's stdout doesn't capture actual failure reasons, so store the log
as well.

Signed-off-by: Jeremy Kerr <[email protected]>
@jk-ozlabs
Copy link
Member Author

Should transitive dependencies like anyio also be added to requirements.txt?

Ideally we'd just have the direct ones, and pip would have some way to lock the transitive ones. I'm not sure if the latter is possible, so maybe freezing everything would be best.

I am unsure how the asyncdbus dependency ended up with a newer anyio package though...

@jk-ozlabs jk-ozlabs merged commit e9988db into CodeConstruct:main Oct 14, 2025
3 checks passed
@jk-ozlabs jk-ozlabs deleted the dev/test-fixes branch October 14, 2025 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants