-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
Create examples.md #763
Merged
Merged
Create examples.md #763
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
Summarize Sui code samples for easy reference and findability
gdanezis
approved these changes
Mar 11, 2022
sblackshear
approved these changes
Mar 11, 2022
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.
Thanks Clay!!
sblackshear
reviewed
Mar 11, 2022
sblackshear
reviewed
Mar 11, 2022
awelc
approved these changes
Mar 11, 2022
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Co-authored-by: Sam Blackshear <sam@mystenlabs.com>
Thanks for the excellent review and edits, Sam! |
mwtian
pushed a commit
that referenced
this pull request
Sep 12, 2022
) We operate an executor with a bound on the concurrent number of messages (see #463, #559, #706). PR #472 added logging for the bound being hit. We expect the executors to operate for a long time at this limit (e.g. in recovery situation). The spammy logging is not usfeful This removes the logging of the concurrency bound being hit. Fixes #759
mwtian
pushed a commit
to mwtian/sui
that referenced
this pull request
Sep 29, 2022
…ystenLabs#763) We operate an executor with a bound on the concurrent number of messages (see MystenLabs#463, MystenLabs#559, MystenLabs#706). PR MystenLabs#472 added logging for the bound being hit. We expect the executors to operate for a long time at this limit (e.g. in recovery situation). The spammy logging is not usfeful This removes the logging of the concurrency bound being hit. Fixes MystenLabs#759
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.
Summarize Sui code samples for easy reference and findability