This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Add using is_ready safeguard to get_endpoint docstring
#170
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
mmkay
approved these changes
Sep 17, 2024
michaeldmitry
force-pushed
the
OPENG-2736
branch
from
9563179 to
265cb6a
Compare
michaeldmitry
changed the title
get_endpoint in tracing libraryis_ready safeguard to get_endpoint docstring
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue
Fixes #169
Solution
Add documentation to use the
is_readysafeguard beforeget_endpointto prevent permission denied exceptions due to non-leader units trying to access local app databags.