expose state size bytes when describing standalone activities#9962
Merged
fretz12 merged 1 commit intotemporalio:mainfrom Apr 15, 2026
Merged
expose state size bytes when describing standalone activities#9962fretz12 merged 1 commit intotemporalio:mainfrom
fretz12 merged 1 commit intotemporalio:mainfrom
Conversation
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?
Populated the StateSizeBytes field in buildActivityExecutionInfo from executionInfo.ApproximateStateSize, and added assertions for it across the standalone activity integration tests
Why?
Filling it in gives API consumers visibility into activity state size, which is useful for monitoring resource usage and billing purposes.
How did you test it?