Conversation
|
According to #4843 (comment) only eventlet/gevent workers have this issue. I don't understand this comment, but it looks like your change does not fix the root cause: |
|
this is just a copy of your proposed fix in your fork |
|
@auvipy I see, and it's good for me ;). I'm not 100% sure that it's good for everyone else. |
Codecov Report
@@ Coverage Diff @@
## master #5482 +/- ##
=======================================
Coverage 82.79% 82.79%
=======================================
Files 144 144
Lines 16492 16492
Branches 2057 2057
=======================================
Hits 13655 13655
Misses 2625 2625
Partials 212 212
Continue to review full report at Codecov.
|
|
I opened the pr for more consensus actually |
|
OK let's postpone this for a while! |
|
@auvipy @thedrow Forgive me if I'm wrong, but I'm confused why the technical board team was requested to review this pull request (and others). celery/ceps#13 and CEP 1 described the technical board as solely for high-level (read: CEP-level) decision making to support the core developers, not day-to-day development. This may have been a mistake only, but please let me know it the CEP isn't up-to-date anymore. |
|
the CEP is alright. I am the culprit to request the review here!! |
|
TEST? |
|
What is the outcome when the connection is offline and it will now raise from within publish? What is expected happens next in the exception handling by default? |
|
Team, is there any update about this issue? Was this addressed and fixed in celery 4.4.0? |
|
can you check this #5870 ? |
|
I see , so it seems it is still waiting for a test to be executed and it is still not merged in, I can see the PR is open , correct? |
|
you should try that patch on your staging env |
|
@auvipy thanks for your answer. To be precise this is the type of exception we found, I looked at the solution proposed in the PR and would like to understand if its applicable also to our problem based on the error log or its unrelated issue |
No description provided.