Fix endpoint file path retrieval in get_endpoint function#50
Open
yf23 wants to merge 1 commit into
Open
Conversation
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
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.
This pull request improves the robustness of the endpoint file lookup logic in the
get_endpointfunction. The function now searches multiple directories for the attestation URI table file, ensuring it can be found regardless of the script's execution context.File lookup improvements:
get_endpointinattest.pyto search for the attestation URI table file (attestation_uri_table.jsonorattestation_uri_table_usgov.json) in multiple directories: the directory of the current file, the directory of the script being executed, and the current working directory. If the file is not found, an exception is raised.