-
Notifications
You must be signed in to change notification settings - Fork 49
Dead queue and retry implementation #52
base: master
Are you sure you want to change the base?
Dead queue and retry implementation #52
Conversation
…p to date consumer
…refigueira/rabbitmq-cli-consumer into feature/dead-queue-and-retry
- Remove RPC config from example
… did not have the headers published correctly for queue or exchange
Hi Again, So I've been testing this extensively and spotted a bug in the original PR which caused dead queued items to not have their headers published correctly, have now resolved this in latest push. Cheers |
Thank you for your PR. I would love to get this in, but since there are no tests in the current master I'm very cautious on merging new stuff. A lot of people (including my previous company) are running this in production and I don't want to break things. I'm not using this library actively anymore and I don't have the time to put a lot of effort in it. So it would even be difficult to just compile and test your work. I understand if you want to continue to work on your own fork. If you're interested in contributing perhaps you could take a look at the discontinued v2 rewrite. If you're not interested: no hard feelings 😄 |
Hi @ricbra No hard feelings at all! very grateful for the library to begin with! Wondering, if I were to include tests for everything would that help? I'll take a look at V2 also! to see what's in it. Thanks again |
- Add a gitignore
Hi @ricbra
I took the initial work @mjolt did and put in to the most up to date code. Do you reckon there is a chance of merging it in? I'd love to keep using the original codebase, and contributing, but really need this functionality. So if this isn't merged, then I'll probably just work off of the fork.
Tested for backwards compatibility, and all seems to work perfectly.
Let me know if you'll be merging and if you want me to change anything!
Thank you!