Skip to content

Conversation

@Quinn-With-Two-Ns
Copy link
Contributor

@Quinn-With-Two-Ns Quinn-With-Two-Ns commented Oct 22, 2025

Stop sending deployment info for session per-worker task queue


Note

Temporarily disable deployment versioning on the session’s resource-specific activity worker and restore it for the creation worker; add a test validating Build ID behavior with sessions.

  • Worker (sessions):
    • For session resource-specific task queue, stop including deployment options by disabling params.DeploymentOptions.UseVersioning and params.UseBuildIDForVersioning when creating the session activity worker.
    • Restore original deployment/versioning options before creating the session creation worker.
  • Tests:
    • Add TestBuildIDWithSession verifying workflow execution under session with deployment versioning, plus related activity import.

Written by Cursor Bugbot for commit 5fc9d01. This will update automatically on new commits. Configure here.

@Quinn-With-Two-Ns Quinn-With-Two-Ns marked this pull request as ready for review October 22, 2025 23:36
@Quinn-With-Two-Ns Quinn-With-Two-Ns requested a review from a team as a code owner October 22, 2025 23:36
cursor[bot]

This comment was marked as outdated.

cursor[bot]

This comment was marked as outdated.

params.TaskQueue = sessionEnvironment.GetResourceSpecificTaskqueue()
// For the resource specific task queue, we don't need to include deployment options
// Save them to restore later
deployments := params.DeploymentOptions
Copy link
Contributor

Choose a reason for hiding this comment

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

Only disable versioning instead of removing the whole thing? better to keep the deployment name and build id if user has given it (to keep in the events).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Does it make any difference for an activity only task queue? I don't see any difference in the history.

Copy link
Contributor

Choose a reason for hiding this comment

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

we might add the deployment options in activity events later

}

func (ts *WorkerDeploymentTestSuite) TestBuildIDWithSession() {

Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want to gate this? All other tests here have this req

if os.Getenv("DISABLE_SERVER_1_27_TESTS") != "" {
		ts.T().Skip("temporal server 1.27+ required")
	}

wfHandle, err := ts.client.ExecuteWorkflow(ctx, ts.startWorkflowOptions("evolving-wf-1"), "SessionBuildIDWorkflow")
ts.NoError(err)

ts.NoError(wfHandle.Get(ctx, nil))
Copy link
Contributor

Choose a reason for hiding this comment

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

What is this actually verifying? This seems to pass on master without your fix

Copy link
Contributor

Choose a reason for hiding this comment

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

Should we be asserting that buildId and versioning settings for the session activity worker is properly set?

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.

4 participants