-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport #20 to version 1.x of the GEM #23
Conversation
Hi @pinkahd, thanks for opening this. |
Correct, but GitHub was not showing me the "Approve and run CI" button, so I couldn't approve. |
@pinkahd minor rubocop offenses to fix, should be easy but please let me know if you need help 👍 |
Thanks 🙌🏼 I'll fix those and update the branch. |
(cherry picked from commit ce5e099)
@iMacTia Looks like you'll need to approve the CI again after I've force update the branch, hopefully this this everything will pass 🤞🏼 |
Mmmh something is wrong with |
Hmm noticed that as well, could it be because of the depreciated |
I think that was it, all checks passed with the new |
Thanks for fixing that @pinkahd, all green now 🎉 ! LGTM |
Thanks 🙌🏼 Let me know if you're gonna release version 1.2.1 in ruby gems 😇. Thanks again 💯 |
Amazing! 🎉 |
Hey 👋🏼
We've encountered some issues when we've updated our
sidekiq-unique-jobs
gem to the latest version and it looks like the latest version started sending nested fields issue related #3 Currently we're still stuck on version 5 of Sidekiq so we couldn't update thesidekiq-logstash
gem to version 2.x to get this patch in.This patch is back porting the fix made in #20 to version 1.x as well, I'm thinking there might be other in the same situations that might benefit form this patch as well.
Let me know if you're still interested to support version 1.x of this gem if not I can close this PR and maintain our fork for now.
Thanks