kotfic

Is this an issue that can be resolved downstream at build/deploy time? I would be hesitant to forcibly revert celery versions across all downstream projects.

To be clear, Celery 4.2 and 4.3 - in conjunction with an unknown set of deployment configurations - are showing intermittent errors for _some_ users. Until it is resolved in...

Its not clear what the issue is, there is no consistently reproducible minimum working example of the error.

@manthey Is there a practical reason this can't be mitigated downstream in your project code or is your concern more ideological?

I'm glad to hear that in the short term this can be mitigated downstream. Unless everyone else is secretly having this problem with Girder Worker and just not speaking up...

To test this I recommend the following: ```sh mkdir gwruntest; cd gwruntest # Make a virtualenv mkvirtualenv -a . gwruntest # Clone the repos git clone -b gwrun [email protected]:girder/girder_worker.git git...

Just my two cents, this would be another reason to introduce redis into the mix. Redis has pretty good support for HA distributed locking, and could replace rabbitmq as the...

@manthey Sorry i'm having a little trouble refreshing on the origin of this issue. Is it possible to link to the code where you're seeing the unexpected behavior?

now would also be a good time as there are no major PR's open, or immediately planned

this morning i agreed with @cjh1 about consistency over my preference (snake_case) but i think dan brings up an important point. EIther way we should be ensuring we're consistent throughout...