-
Notifications
You must be signed in to change notification settings - Fork 185
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
Fix: User script import now respects script_dir
#1542
Open
tezheng
wants to merge
2
commits into
microsoft:main
Choose a base branch
from
tezheng:fix/import_user_script
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
@tezheng commenting on this file so we can have a thread.
Your proposal for allowing user_script paths relative to the directory containing the config json makes a lot of sense. It would help a lot with the portability of olive projects.
However, apart from user_scripts, we also have many other resources like data dirs, script dirs, etc that have the same issue. Workflows can also be run on remote systems such as docker and azureml, both of which require resolvable paths for mounting. Due to this, we originally decided on paths that are absolute or relative to current dir so that every resource is resolvable and independent of one another.
After a discussion with the team, we agree that allowing paths to be relative to the working directory (directory containing config json) should also be supported. I have created a work item for this, and we can discuss offline on teams with you about the priority of this feature. This would require a more involved update of the entire codebase so that all resources have the same behavior (+ not have user script be a special case) and don't break compatibility with remote systems.
FYI this is how we infer resource types. This would need to be updated to check for paths relative to the working dir. There are also other
Path.resolve()
instances throughout the codebase that we would need to updated accordingly.