-
Notifications
You must be signed in to change notification settings - Fork 125
feat(worker): Add a workflow metadata query #1319
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
Merged
antlai-temporal
merged 12 commits into
temporalio:main
from
antlai-temporal:add-get-workflow-metadata
Jan 18, 2024
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
6b21407
Add a workflow metadata query
antlai-temporal d016991
Merge branch 'main' into add-get-workflow-metadata
mjameswh f447b04
Merge remote-tracking branch 'upstream/main' into add-get-workflow-me…
antlai-temporal 9047d65
Track current sdk-core version
antlai-temporal 58e71f3
Update sdk-core to removed dbg()
antlai-temporal bfeab6a
Remove ad-hoc types
antlai-temporal d79dd8d
Merge remote-tracking branch 'upstream/main' into add-get-workflow-me…
antlai-temporal eabbe0b
Fix format
antlai-temporal 0c3a6b5
Remove workflow description for memo
antlai-temporal 8fcc7fb
Merge remote-tracking branch 'upstream/main' into add-get-workflow-me…
antlai-temporal 4f99a9c
Remove AnyhandlerOptions
antlai-temporal 964d46b
Merge remote-tracking branch 'upstream/main' into add-get-workflow-me…
antlai-temporal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's getting messy. I think we should consider not listing "internals" queries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could be useful for knowing what built-in queries, like
__temporal_workflow_metadata
, are supported by the WF.Also the UI today may expect some handlers present when parsing the error message...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UI doesn't and shouldn't expect specific handlers to be present in the list returned on query not found error message. Using that error message to report existing queries is hack, not normalized across SDKs, and going forward, UI should call
__temporal_workflow_metadata
directly anyway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with you on the UI, but unfortunately, depending on how the UI parses the query today, we may break it if we return an empty set. It is also unfortunate that
isBlocked
does not have the__
internal prefix. Once they switch, we can do the cleanup with them...Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Fixing the query-failed string to not include all queries anymore should be a separate task once we feel comfortable enough modern UIs are no longer using it (i.e. fixed version has been out there a while). There are other approaches too such as having this error return the workflow metadata as extra error details. Hrmm, I wonder if we should do that...can discuss separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My point was not about query-failed no longer returning any queries, but only about not returning SDK built-in queries. For example, if using an old UI, they should not see
__stack_trace
,__enhanced_stack_trace
and__temporal_workflow_metadata
in the query drop down. Returning user queries is still fine, for now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If needed that's easy to filter by the UI using the
__
prefix. I like that we can quickly know what internal queries are supported for a given workflow...