4 ms·

Amazing news and congrats to the devs! We rely on Celery to handle about 700k tasks daily and it has not failed us once. However, if anyone from the maintainer

Amazing news and congrats to the devs! We rely on Celery to handle about 700k tasks daily and it has not failed us once. However, if anyone from the maintainers is reading - could you guys please have auvipy not deliberately close outstanding issues / PRs that he thinks are not important and that other maintainers then proceed to re-open. Disclosure: I got banned for pointing that out only, so I may be slightly biased. [0] 0 - https://github.com/celery/celery/issues/4817#issuecomment-472516894 https://github.com/celery/celery/issues/4817#issuecomment-47...

gamegod 6y ago
Yeah, this bit me in the ass too. They close bugs that are valid but they just don't want to fix, so looking at their bug tracker gives you a misrepresentation of their project. It's a poor practice, and I've been hit by bugs in production that were closed in their bug tracker. Also, you really need to read the fine print to understand the quirks of every backend (eg. Redis) when using Celery. For me, this plus the above means I'll never use Celery again.
- sjansen 6y ago
  We've learned through painful experience to treat Celery as little more than a vanilla pub/sub system. Some of its more "advanced" features sound nice, until you discover they're implemented in surprising or unscalable ways. They've gotten better at documenting some of these gotchas, but at this point we've been burned one too many times. I'm hopeful 2021 is the year we eliminate Celery from our system.
  - belval 6y ago
    If you add up every hour I spent debugging celery in a production system, I could probably just rewrite it with the few features I was actually using. It's a terrible piece of open source as it "looks" fine from the outside, you integrate it and then you start getting weird stability issues that are super hard to debug.

4 ms·

Amazing news and congrats to the devs! We rely on Celery to handle about 700k tasks daily and it has not failed us once. However, if anyone from the maintainer

by bkovacev 6y ago

gamegod 6y ago
Yeah, this bit me in the ass too. They close bugs that are valid but they just don't want to fix, so looking at their bug tracker gives you a misrepresentation of their project. It's a poor practice, and I've been hit by bugs in production that were closed in their bug tracker. Also, you really need to read the fine print to understand the quirks of every backend (eg. Redis) when using Celery. For me, this plus the above means I'll never use Celery again.
- sjansen 6y ago
  We've learned through painful experience to treat Celery as little more than a vanilla pub/sub system. Some of its more "advanced" features sound nice, until you discover they're implemented in surprising or unscalable ways. They've gotten better at documenting some of these gotchas, but at this point we've been burned one too many times. I'm hopeful 2021 is the year we eliminate Celery from our system.
  - belval 6y ago
    If you add up every hour I spent debugging celery in a production system, I could probably just rewrite it with the few features I was actually using. It's a terrible piece of open source as it "looks" fine from the outside, you integrate it and then you start getting weird stability issues that are super hard to debug.