Return NamespaceNotFound error from RespondWorkflowTaskCompleted handler #2810
Conversation
This file contains 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
alexshtin
force-pushed
the
fix/wt-ns-not-found
branch
from
57b56f6
to
33c304c
Compare
wxing1292
approved these changes
May 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Return
NamespaceNotFounderror fromRespondWorkflowTaskCompletedhandler.Why?
There are few places where
NamespaceNotFoundcan be returned from namespace registry. Previously it was substituted withUnavailableerror and it introduces inconsistency. Original error should be returned to the caller instead.How did you test it?
Existing tests.
Potential risks
No risks.
Is hotfix candidate?
No.