Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass errors to the child workflow execution future #1058

Merged
merged 2 commits into from
Mar 16, 2023

Conversation

Quinn-With-Two-Ns
Copy link
Contributor

Pass errors to the child workflow execution future. I had to version this because the change is technically non deterministic, I don't know if anyone would hit is, but I also don't understand why people launch duplicate child workflows so I am playing it safe.

resolves: #1041

return nil
}

func DuplicateChildWorkflow(ctx workflow.Context) error {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This workflow will replay differently before and after my change, hence the use of SDK flags.

Copy link
Contributor

@mmcshane mmcshane left a comment

Choose a reason for hiding this comment

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

LGTM, Just the comment thing

internal/internal_flags.go Outdated Show resolved Hide resolved
@Quinn-With-Two-Ns Quinn-With-Two-Ns merged commit 91636e4 into temporalio:master Mar 16, 2023
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.

Workflow got hanged if spawn childWorkflow with same workflowId
2 participants