CRAYSAT-1649: Added ability for paths with a ~ to be unwrapped #48
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
7 tasks
haasken-hpe
approved these changes
Dec 9, 2024
… to be parsed correctly
ethanholen-hpe
force-pushed
the
CRAYSAT-1649
branch
from
79b963f to
9c64c59
Compare
ethanholen-hpe
changed the title
|
/backport release/2.3 |
|
Backporting into branch release/2.3 was successful. New PR: #51 |
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.
Summary and Scope
add error logging when unable to find token file path and unwrap ~ as home directory
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
<insert branch name here>Testing
List the environments in which these changes were tested.
Tested on:
Test description:
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
No
Pull Request Checklist