- Refresh task queue first before get task from queue [2434b44]
- Update documentation link for
aio-pika
inventory [18248d4]
- Drop support for Python 3.7 [8adf324]
- Update requirement
aio-pika~=9.0
[e6538e6] - Update
isort==5.12.0
[bb0c7b6]
- Update ReadTheDocs configuration file [8a7bcf6]
- Restore intended interface of
RmqThreadCommunicator
[#124]
RmqThreadCommunicator
: remove deprecatedstart
andstop
methods [#125]
- Remove obsolete
release.sh
[#115] - Merge separate license files into one [#116]
- Add the
isort
pre-commit hook [#118] - Move package into the
src/
subdirectory [#119] - Update the continuous deployment workflow [#121]
- Add support for Python 3.10 and 3.11 [#130]
- Update requirement
pytest-notebook>=0.8.1
[#130] - Unpin requirement
docutils
[#130] - Update requirement
pytest~=6.0
[#130] - Update requirement
pyyaml~=6.0
[#130]
- Dependencies: restrict ranges of
aio-pika<6.8.2
andpamqp~=2.0
[#108]
- Drop support for Python 3.6 [#108]
RmqCommunicator
: add theserver_properties
property [#107]- Expose
aio_pika.Connection.add_close_callback
[#104]
- ♻️ REFACTOR: BroadcastFilter to extract filter conditions into a separate
is_filtered
method.
- 👌 IMPROVE: Add debug logging for sending task/rpc/broadcast to RMQ.
- 👌 IMPROVE: Close created asyncio loop on RmqThreadCommunicator.close
- 🐛 FIX: an aio-pika deprecation, to use async context managers when processing messages.
The default task message TTL setting was changed in v0.5.4
but this breaks existing queues since RabbitMQ does not allow changing these parameters on existing queues.
Therefore the change was reverted which was released in v0.5.5
.
However, since that was a patch release, it had not been merged back to v0.6.0
as well, which therefore from the problem described.
The same revert is applied in this release to restore original functionality.
- Revert "Increase the default TTL for task messages" [#93]
- Add support for Python 3.9 [#87]
- Drop support for Python 3.5 [#89]
- Replace old format string interpolation with f-strings [#90]
- Fix warning caused by excepted task and no reply [#83]