refactor: examples error handling #64
Merged
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
myungjin
reviewed
Aug 2, 2024
|
This PR is not a feature. This PR is mostly refactoring. So, please update the commit title in git. |
myungjin
changed the title
raresgaia123
force-pushed
the
examples_error_handling
branch
3 times, most recently
from
ebf52e0 to
828f13b
Compare
added error handling for examples updated ccl operaions with rank 0 as the actor updated logs for a better understanding of the operations
raresgaia123
force-pushed
the
examples_error_handling
branch
from
828f13b to
f825387
Compare
myungjin
approved these changes
Aug 6, 2024
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.
added error handling for examples
updated ccl operaions with rank 0 as the actor
updated logs for a better understanding of the operations
Description
Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to
related issues, other PRs, or technical references.
Note that by not including a description, you are asking reviewers to do extra work to understand the context of this
change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all.
Type of Change
Checklist