Add unimplemented DiagnoseWorkflowExecution methods - #1015
Merged
c-warren merged 4 commits intoAug 1, 2025
Conversation
c-warren
requested review from
Groxx,
abhishekj720,
demirkayaender,
dkrotx,
natemort,
shijiesheng and
taylanisikdemir
as code owners
July 31, 2025 16:47
c-warren
marked this pull request as draft
July 31, 2025 20:20
c-warren
marked this pull request as ready for review
August 1, 2025 02:18
shijiesheng
approved these changes
Aug 1, 2025
pandeyanshuman
pushed a commit
to pandeyanshuman/cadence-java-client
that referenced
this pull request
Oct 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Why?
This is the first step in updating the client to the latest IDL package, as of July 31. This chunk has been chosen to expose the QueryConsistencyLevel on DescribeWorkflowExecution and GetWorkflowExecutionHistoryRequest - coming in a follow up PR while minimizing the number of breaking changes consumed.
How did you test it?
Unit tests + build.
Potential risks
There are a lot of IDL changes being pulled in (approximately a years worth). While there are few actual implementation changes it's still a concerningly long list.
Release notes
N/A
Documentation Changes
N/A