| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
updates:
- [github.com/PyCQA/autoflake: v2.0.1 → v2.0.2](https://github.com/PyCQA/autoflake/compare/v2.0.1...v2.0.2)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* updated python versiions in CI
* updated python versiions in CI with
* updated tox
* updated ci
* Update .github/workflows/ci.yaml
* Update .github/workflows/ci.yaml
* Update .github/workflows/ci.yaml
|
|
|
|
| |
3.10. Ref #1663.
|
|
|
| |
Refs #1590
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* refactor: Refactor utils/json
* Update kombu/utils/json.py
* Update kombu/utils/json.py
* chore: Use older syntax (no walrus)
* chore: Update doscstrings
* chore: Fix pydocstyle complaints
* chore: Restore previous docstring
|
|
|
|
|
| |
Looks like `_setupfuns` is unused and should be removed.
If they're used somehow, please explain how, so i can add comment here to avoid future confusion.
|
| |
|
|
|
|
|
|
| |
updates:
- [github.com/PyCQA/autoflake: v2.0.0 → v2.0.1](https://github.com/PyCQA/autoflake/compare/v2.0.0...v2.0.1)
- [github.com/pycqa/isort: 5.11.4 → 5.12.0](https://github.com/pycqa/isort/compare/5.11.4...5.12.0)
|
|
|
|
|
|
|
| |
In MaybeChannelBound, the `__call__()`, `bind()` and `maybe_bind()` methods
takes a channel argument. The type annotation say this argument must be a
Channel, but it goes through `maybe_channel()`, so it can also be a
Connection. Update the annotation to accept both Channel and Connection.
|
|
|
|
|
|
|
| |
* sqlalchemy==1.4.46
* Update requirements/extras/sqlalchemy.txt
* bump
|
|
|
|
|
|
|
|
|
|
|
| |
* support sqla v2.0
* Update kombu/transport/sqlalchemy/models.py
* update (#1652)
---------
Co-authored-by: Asif Saif Uddin <auvipy@gmail.com>
|
| |
|
| |
|
| |
|
|
|
| |
Per https://github.com/celery/kombu/pull/1632 @thedrow asked to add this argument so `Optional` is still used.
|
|
|
|
|
|
| |
updates:
- [github.com/pycqa/isort: v5.11.3 → 5.11.4](https://github.com/pycqa/isort/compare/v5.11.3...5.11.4)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
imports (#1637)
* add autoflake to .pre-commit-config.yaml to automatically remove unused imports
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|
|
|
|
|
| |
* add managed identity support to azure storage queue
* flake8 fixes
|
|
|
|
|
| |
* redis==4.3.4 temporarilly in an attempt to avoid bc
* redis>=4.2.2,<4.4.0
|
|
|
|
|
| |
updates:
- [github.com/pycqa/isort: 5.10.1 → v5.11.3](https://github.com/pycqa/isort/compare/5.10.1...v5.11.3)
|
|
|
|
|
|
|
|
|
| |
policy (#1629)
* Added unit test: test_ensure_retry_errors_is_not_looping_infinitely()
* Added unit test: test_ensure_retry_errors_is_limited_by_max_retries()
* Added retry_errors arg to Connection.ensure() to allow applying retry policy for specific errors additionally
|
|
|
|
|
|
|
| |
updates:
- [github.com/asottile/pyupgrade: v3.2.0 → v3.3.1](https://github.com/asottile/pyupgrade/compare/v3.2.0...v3.3.1)
- [github.com/PyCQA/flake8: 5.0.4 → 6.0.0](https://github.com/PyCQA/flake8/compare/5.0.4...6.0.0)
- [github.com/pre-commit/pre-commit-hooks: v4.3.0 → v4.4.0](https://github.com/pre-commit/pre-commit-hooks/compare/v4.3.0...v4.4.0)
|
|
|
|
|
|
|
| |
* pin sqlalchemy==1.4.44
* sqlalchemy==2.0.0b4
* sqlalchemy==1.4.45
|
| |
|
|
|
|
|
| |
updates:
- [github.com/asottile/pyupgrade: v3.1.0 → v3.2.0](https://github.com/asottile/pyupgrade/compare/v3.1.0...v3.2.0)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
updates:
- [github.com/asottile/pyupgrade: v3.0.0 → v3.1.0](https://github.com/asottile/pyupgrade/compare/v3.0.0...v3.1.0)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
docker-compose (#1611)
* Parse credential as a dict when using Azurite emulator
This more flexible credential allows the use of Azurite for integration testing in local docker-compose configurations.
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Fix some lint errors
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
| |
updates:
- [github.com/asottile/pyupgrade: v2.37.1 → v3.0.0](https://github.com/asottile/pyupgrade/compare/v2.37.1...v3.0.0)
- [github.com/PyCQA/flake8: 4.0.1 → 5.0.4](https://github.com/PyCQA/flake8/compare/4.0.1...5.0.4)
- [github.com/asottile/yesqa: v1.3.0 → v1.4.0](https://github.com/asottile/yesqa/compare/v1.3.0...v1.4.0)
|
|
|
|
|
| |
Python's `del` is a statement, not a function, and doesn't need
parenthesis.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add separate transport option for retry loop timeout
This only applies when using `Connect.default_channel`.
Before this change, the retry loop timeout was set equal to TCP connect timeout (`connect_timeout`), meaning when first connection attempt timeouted, no retry would be attempted.
Now if a new transport option `connect_total_timeout` is provided, this overrides `connect_timeout` for the retry loop (but not for TCP connect).
* Add tests
* Fix isort
* Rename to connect_retry_timeout
* Reformat
* connect_retry_timeout -> connect_retries_timeout
* Fix flake8
|
|
|
|
|
| |
* importlib_metadata removed deprecated entry point interfaces
* importlib-metadata usage requires 3.6
|
|
|
|
|
|
| |
partly fix: #398
1. add exclusive lock during the whole exchange file update.
2. add some unit test for file lock
|
|
|
|
|
|
|
| |
Otherwise Celery jobs start to get `datetime` in place of `date` and that
could lead to errors.
See https://github.com/celery/celery/issues/7754, related PR #1515.
|
|
|
| |
This reverts commit 8699920e050727d385a6d5a19c939e55a86688d6.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Solve Kombu filesystem transport not thread safe
fix: #398
Currently only write lock used in msg/exchange file written. Cause
reading in other thread got some incomplete result.
1. Add timeout for the lock acquire.
2. Add Share locks when reading message from filesystem.
3. Add a unit test for the `lock` and `unlock`
4. Add a unit test to test the lock during message processing.
* Replace deprecated function.
|
|
|
|
|
| |
* Accept *args in disconnect()
* Add test for redis connection timeout error
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* hub: tick delay fix
todo and timer callbacks can perform actions that
require a tick callback to be executed right away
without polling.
the current order can cause issues
when using single worker with no prefetch (acks late).
related issue in celery:
https://github.com/celery/celery/issues/7718
* add unit test for hub delay fix
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Avoid losing type of UUID when serializing/deserializing
Serializing UUIDs as strs and deserializing them as strs can lead to
somewhat obscure bugs such as the one that led to the creation of this
PR in django-cacheback
https://github.com/codeinthehole/django-cacheback/pull/100 which some
would call unexpected behaviour.
After all, an UUID is altogether a different type from strs and if
bytes got their own serializer/deserializer for UUID the same logic
should apply.
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Update documentation for JSON serialization
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|