Skip to content

Conversation

@shijiesheng
Copy link
Member

What changed?

additional test to show case how decisions are processed in batches.

Why?

So the same test scenarios could be shared by other SDKs.

How did you test it?

unit test

Potential risks

Release notes

Documentation Changes

Signed-off-by: Shijie Sheng <liouvetren@gmail.com>
Signed-off-by: Shijie Sheng <liouvetren@gmail.com>
shijiesheng added a commit to cadence-workflow/cadence-python-client that referenced this pull request Nov 13, 2025
<!-- Describe what has changed in this PR -->
**What changed?**

* re-implementing the batching logic

<!-- Tell your future self why have you made these changes -->
**Why?**

current implementation has problems and is based off java SDK with
confusing naming.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**

Unit Test that matches java SDK
cadence-workflow/cadence-java-client#1035

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**

<!-- Is it notable for release? e.g. schema updates, configuration or
data migration required? If so, please mention it, and also update
CHANGELOG.md -->
**Release notes**

<!-- Is there any documentation updates should be made for config,
https://cadenceworkflow.io/docs/operation-guide/setup/ ? If so, please
open an PR in https://github.com/cadence-workflow/cadence-docs -->
**Documentation Changes**

---------

Signed-off-by: Shijie Sheng <liouvetren@gmail.com>
@shijiesheng shijiesheng merged commit b457361 into cadence-workflow:master Nov 13, 2025
7 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