Skip to content

WIP: Add nexus-operation-with-standalone-activity to throughput_stress#410

Draft
tekkaya wants to merge 1 commit into
mainfrom
gtekkaya/nexus-standalone-activity-throughput-stress
Draft

WIP: Add nexus-operation-with-standalone-activity to throughput_stress#410
tekkaya wants to merge 1 commit into
mainfrom
gtekkaya/nexus-standalone-activity-throughput-stress

Conversation

@tekkaya

@tekkaya tekkaya commented Jun 23, 2026

Copy link
Copy Markdown

No description provided.

Adds an `include-nexus-standalone-activity` throughput_stress option that
exercises a Nexus operation whose handler starts a standalone activity (via
StartActivityExecution) and attaches a completion callback so the activity's
completion asynchronously resolves the operation. The operation is driven both
as an in-workflow Nexus operation and as a standalone Nexus operation, mirroring
bench-go's EnableNexusOperationWithStandaloneActivity (NEXUS-434) and the open
canary-go nexus-standalone-activity work.

- New StandaloneActivityNexusOperation (name "standalone-activity") on the Go
  worker's kitchen-sink Nexus service. Input/output types match the echo
  operations so it is invocable through both existing omes Nexus paths with no
  client-executor changes.
- throughput_stress flag, validation, and two invocation paths wired into the
  parallel async action block.
- Integration test exercising the full flow end-to-end against the dev server
  with activity.enableStandalone + activity.enableCallbacks dynamic config.
- README documentation.
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.

1 participant