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
Fix dynamodb HA lock race #5829
Conversation
I'm still testing this change, opened to start the discussion. I'll ping back when tested fully. |
I've tested this and deployed it to production and it works as expected. |
@mahmoudm Thanks for digging in to this. I've reviewed it briefly and it looks reasonable. Can you please add a test to |
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Mahmoud Abdelsalam seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
Hi @mahmoudm would you be able to find time to finish the PR ? |
@mahmoudm Thanks for working to help clear the CLA block. It looks like some older commits are under another GitHub ID that's no longer active. Would you mind taking your current code and pushing a new PR, squashed without reference to the old ID? We can then close out this PR and I'll help integrate the new one. |
97fa2d7
to
32bdc51
Compare
should be good now - LMK if this doesn't work |
@mahmoudm Despite the force-push and the history only showing the one commit, the CLA checker is still referencing the old email. Could you push the work (i.e the same squashed commit, possibly as a new branch in your repo) as a new PR? I think that may be simplest way to appease the CLA checker. Thanks for your patience with this! |
ok, opened here: #6512 |
Fixes #5828