-
Notifications
You must be signed in to change notification settings - Fork 198
Priorities for Workflows/Activities #2453
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
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
54956a8
Update protos
Sushisource 436cf0e
Add priority to various options
Sushisource b0237c4
Update proto to tagged version
Quinn-With-Two-Ns 23a353d
Fix a bunch of bugs and refactor to be more consistent with the rest …
Quinn-With-Two-Ns db9831b
Update test and test server impl.
Quinn-With-Two-Ns 8cecb81
Switch CI to prerelease CLI
Quinn-With-Two-Ns eb66e34
try some dynamic configs
Quinn-With-Two-Ns a5d4cb6
Add SA
Quinn-With-Two-Ns 1b37395
fix
Quinn-With-Two-Ns e40de55
try again
Quinn-With-Two-Ns fe6c93b
remove stupid x
Quinn-With-Two-Ns 51cbf01
Add delay
Quinn-With-Two-Ns 9a034bb
try again
Quinn-With-Two-Ns 31c9b35
Add port
Quinn-With-Two-Ns 8001bf9
update
Quinn-With-Two-Ns 904ddb5
tweaks
Quinn-With-Two-Ns c607e28
last one
Quinn-With-Two-Ns 22a5936
Disable eager execution for priority test
Quinn-With-Two-Ns 860e179
Fix other tests
Quinn-With-Two-Ns 534ba73
fix
Quinn-With-Two-Ns 84fc329
fix nexus
Quinn-With-Two-Ns 86a1864
t
Quinn-With-Two-Ns 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
Oops, something went wrong.
Oops, something went wrong.
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.
What situations is this nullable? Old servers only or always unless explicitly set? (just curious, though if confusing we should consider documenting the cases where it may be)
Also a bit confused on this class how a user can know whether a return is nullable or not. But given the confusion, best to be safe and make it clear in docs. I would consider
Optional<Priority>if it can be nullable even on newer servers, but meh. Note this same concern does apply as much to user-set values like the activity options.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 it can be nullable we should bias towards tagging with
@Nullablevs optional, it is the preferred approach in JavaThere 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 can be nullable insofar as you might be using an old server. So, yeah I'll attach the annotation. I believe new servers will always attach the (default) value.
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.
Would be worth documenting that and verifying the test server does match the real server here
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.
So server leaves this as
nullif unset which is the equivalent of default. In Go, if the server left it as null, we return the default object so I did the same hereThere 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 think we need to not do that as it will lie. The default values for priorty are not 0, and therefore we might lie and seem like they've been set to zero for a server that actually just doesn't understand priority
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.
Zero means default, so zero is not a lie