Skip to content

Conversation

@eleonoradgr
Copy link
Contributor

What changed?
Extending the transaction with operation in the else branch to get the state in case the comparison fails

Why?
we need to understand why there is a conflict when we assign the shards but it is not possible because etcd is not showing which is the failing comparison, so we need to be able to understand where the conflict is generated

How did you test it?
unit tests that cover this case actually reported the mismatch

Potential risks

Release notes

Documentation Changes

@eleonoradgr eleonoradgr changed the title chore(shard-distirbutor) : extend info to debug assignment conflicts chore(shard-distirbutor): extend info to debug assignment conflicts Dec 3, 2025
Copy link
Contributor

@arzonus arzonus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@eleonoradgr eleonoradgr merged commit 46d0f64 into cadence-workflow:master Dec 5, 2025
42 of 43 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants