Closed ltalirz closed 1 year ago
Hm... @unkcpz looks like the jupyter notebook test now fails across all python/rabbitmq versions.
It's not clear to me what changed - the last passing commit is from Jan 17 2022. At that point, the latest aio-pika release was 6.8.1 (here we're now installing 6.8.2); I can't really imagine that this is the difference?
The only other thing I notice is that aio-pika 6 is using a somewhat dated version of aiormq (3.3.1) from 2020. Today, aiormq 6 is already out.
Merging #110 (915fdda) into develop (adf373e) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## develop #110 +/- ##
========================================
Coverage 90.32% 90.32%
========================================
Files 16 16
Lines 1146 1146
========================================
Hits 1035 1035
Misses 111 111
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
Wow - either the problem was introduced in aio-pika 6.8.2 or the test is not reproducible.
@sphuber @chrisjsewell Could one of you review this please?
Just for the record, the jupyter notebook test also fails with the combination aio-pika 6.8.2 and pamqp 2 (which was not tested in this PR).
Correct
Do you guys mean that this PR with upper limit <6.8.2
needs a patch release and then #113 with ~=8.0
should be a new minor release?
Yes (upper limit is both for aio-pika and for pamqp, both of which currently break kiwipy)
Ok great, thanks. Want me to take care of merging and making a release?
That would be great, thanks Seb!
fixes #94 fixes #111 see also #112
CI tests fail with recent versions of aio-pika (e.g. version 8) due to API changes.
Furthermore, the Jupyter notebook test from the test suite seems to reproducibly fail with aio-pika version 6.8.2 but pass with aio-pika 6.8.1 (see commits in PR).
Also, kiwipy depends directly on
pamqp
because of this single check:https://github.com/aiidateam/kiwipy/blob/adf373e794ed69d5ec21d4875514971f32d7734f/kiwipy/rmq/threadcomms.py#L261
This dependency was not made explicit in the
setup.py
, and the pre-commit pylint checks alert us to the fact that the API of pamqp 3 has changed.