summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* autopep8.remove-python2-supportOmer Katz2020-08-0419-27/+25
|
* Run tests with PyPy 3.6-7.3.1.Omer Katz2020-08-041-3/+3
|
* Restore this import compatibility code.Omer Katz2020-08-041-1/+5
| | | | This was removed because I thought it's for Python<3 but it's for Python<3.7.
* Merge branch 'master' into remove-python2-supportOmer Katz2020-07-303-5/+9
|\
| * flake8: noqa the Python 2-only builtins (#1228)4.xChristian Clauss2020-07-283-8/+8
| | | | | | | | | | | | | | | | | | * flake8: noqa the Python 2-only builtin cmp() * flake8: buffer() was removed in Python 3 * flake8: unicode() was removed in Python3 because all str are Unicode Adds the modifications from #1227
| * buffer() was removed in Python 3 so use bytes (#1218)Christian Clauss2020-07-281-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * buffer() was removed in Python 3 so use memoryview https://docs.python.org/2.7/library/stdtypes.html#memoryview-type * buffer = bytes on Python 3 * from kombu.five import buffer * buffer --> buffer_t * @patch('buffer_t') in test_qpid.py * @patch('kombu.five.buffer_t') * Use buffer on legacy Python and bytes on Python * Update test_qpid.py
| * tox.ini: Lint on Python, not on legacy Python (#1217)Christian Clauss2020-07-282-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * tox.ini: Lint on Python, not on legacy Python * Travis CI: Lint on Python, not on legacy Python * Update .travis.yml * Update .travis.yml Co-authored-by: Omer Katz <omer.drow@gmail.com> * flakeplus only works on legacy Python Co-authored-by: Omer Katz <omer.drow@gmail.com>
* | Remove flakeplus from the build.Omer Katz2020-07-302-3/+0
| |
* | Adjust setup.py.Omer Katz2020-07-301-8/+5
| |
* | Drop testing for Python < 3.6.Omer Katz2020-07-302-41/+11
| |
* | Delete five.Omer Katz2020-07-231-6/+0
| |
* | Remove five usage from tests.Omer Katz2020-07-2320-90/+37
| |
* | Remove five usage from kombu/.Omer Katz2020-07-2317-70/+43
| |
* | Remove five usage from kombu/utils.Omer Katz2020-07-2310-136/+55
| |
* | Remove five usage from kombu/transport.Omer Katz2020-07-2319-52/+38
| |
* | Remove five usage from kombu/asynchronous.Omer Katz2020-07-237-22/+10
| |
* | pyupgradeOmer Katz2020-07-13158-617/+360
|/
* Add an SQS transport option for custom botocore configKrzysztof Jagiello2020-07-012-1/+30
|
* v4.6.11v4.6.11Asif Saif Uddin (Auvi)2020-06-244-4/+4
|
* changelog for v4.6.11Asif Saif Uddin (Auvi)2020-06-241-1/+12
|
* Improve mention for MongoDB transport mention in docsDefteZ2020-06-142-2/+4
|
* Revert incompatible changes in #1193 and additional improvements (#1211)Matus Valo2020-06-106-29/+88
| | | | | | | * Revert incompatible changes introduced in #1193 * Improved integration tests covering connection * Fix unittests on python2 + flake8 fixes
* default_channel should reconnect automatically (#1209)Matus Valo2020-06-053-0/+19
|
* v4.6.10v4.6.104.6.9Asif Saif Uddin (Auvi)2020-06-034-4/+4
|
* changelog for 4.6.10Asif Saif Uddin (Auvi)2020-06-031-0/+13
|
* Merge branch 'master' of https://github.com/celery/kombuAsif Saif Uddin (Auvi)2020-06-033-15/+77
|\
| * reuse connectionConor Stevenson2020-06-022-1/+5
| |
| * set _connection in _ensure_connection (#1205)v4.6.9Conor Stevenson2020-06-012-2/+5
| | | | | | Co-authored-by: Conor Stevenson <conor@lendingblock.com>
| * Improved Consumer user guideMatus Valo2020-06-011-13/+68
| |
* | remove un supported classifierAsif Saif Uddin (Auvi)2020-06-031-1/+0
|/
* v 4.6.9Asif Saif Uddin (Auvi)2020-06-014-4/+4
|
* update changelog for 4.6.94.6.9Asif Saif Uddin (Auvi)2020-06-011-1/+1
|
* update changelogAsif Saif Uddin (Auvi)2020-06-011-1/+36
|
* update pyamqpAsif Saif Uddin2020-06-011-1/+1
|
* Fix broken compatibility with CeleryMatus Valo2020-06-012-11/+21
|
* Ensure connection when connecting to brokerMatus Valo2020-06-015-62/+108
|
* Fix for issue #1198: Celery crashes in cases where there aren’t enough ↵Ihar Nauros2020-05-272-6/+90
| | | | | | | | | | | | | | | available workers to start acting on “in-flight” messages in the SQS queue (#1199) * Fix for the issue #1172 * Unit test for the fix relating to the issue #1172 * Fix for issue #1198: Celery crashes in cases where there aren’t enough available workers to start acting on “in-flight” messages in the SQS queue * Fix for issue #1198: fixed lint issues * Fix for issue #1198: added unit tests Co-authored-by: inauros <inauros@copyright.com>
* Fix connection imaybe_declare (#1196)Oleh Kuchuk2020-05-262-0/+19
|
* Revert "Raise RecoverableConnectionError in maybe_declare with retry on and ↵Matus Valo2020-05-252-19/+0
| | | | | dropped connection" (#1195) This reverts commit 90f51bcbbd32146998e7c7e4491150344343776b.
* Fix: eliminate remaining race conditions from SQLAlchemy ChannelAntoine Busque2020-05-171-15/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Although a race condition in the SQLAlchmey Channel class was fixed in a recent commit [0], a few other methods are also susceptible to race conditions. Indeed, if multiple threads call the class' `_open` method, a conflict can occur with the `metadata.create_all` call which creates the schema in the database, resulting in an exception which can look like this: ``` sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "pg_type_typname_nsp_index" DETAIL: Key (typname, typnamespace)=(queue_id_sequence, 2200) already exists. ``` Similarly, `_get_or_create` is susceptible to a race condition if two threads try to create the unique queue object in the database at the same time, resulting in this kind of exception: ``` sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "kombu_queue_name_key" DETAIL: Key (name)=(celery) already exists. [SQL: INSERT INTO kombu_queue (id, name) VALUES (nextval('queue_id_sequence'), %(name)s) RETURNING kombu_queue.id] [parameters: {'name': 'celery'}] ``` By using the mutex, we can ensure that only one thread at a time executes these critical sections, eliminating the race conditions. The mutex has been made re-entrant since `_open` can be called from `_get_or_create`, which would cause a deadlock if a simple `Lock` was used instead of `RLock`. [0] 8f1de37a08318d388a048341ddca12af30019bf3 Signed-off-by: Antoine Busque <antoinebusque@gmail.com>
* Modified Mutex to use redis LuaLock implementationVinay Karanam2020-05-172-58/+44
| | | | Fixes #1190
* Fix flake8Matus Valo2020-05-151-1/+1
|
* Improve integration test suitMatus Valo2020-05-151-1/+17
|
* fix 100% cpu usage on linux while using sqsAndrii Maletskyi2020-05-152-37/+50
| | | | fix https://github.com/celery/celery/issues/5299
* Improved Priority integration testsMatus Valo2020-05-132-26/+35
|
* Fix flake8Matus Valo2020-05-123-11/+11
|
* Added priority integration tests for RedisMatus Valo2020-05-122-7/+96
|
* Added integration tests for priority queuesMatus Valo2020-05-082-1/+91
|
* Added TTL integration testsMatus Valo2020-05-062-1/+56
|
* Added Integration tests for direct, topic and fanout exchange typesMatus Valo2020-05-063-2/+104
|