Remove provider/channel push/pull of files #3690
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
This has been a basically dead code path since removal of non-remote channels: Either a user chooses to not move files (overriding move_files to False) and the push_file was not used. Or the default push_file was used, but: * this is always LocalChannel now (PR #3677) * the script directory is always the local script directory (PR #3688) and so the local channel code always skips making a copy This commit simplies all of that away into using the script path directly with putting it through the above complicated no-op.
|
@ryanchard any chance you could test the PBS bit of this? (specifically, verify that you can make parsl submit PBS jobs ok still?) @yadudoc you're listed as technical sponsor (#2554) for a bunch of these changed providers - can you review those? |
|
I tried this on Polaris to test PBS and it all worked great. |
|
@yadudoc wakey wakey - I'd like to get the rest of channel removal done before the Parsl maintenance work ends in May. |
benclifford
changed the title
|
Treating LSF/SGE/Torque as abandoned as far as this PR goes. |
khk-globus
approved these changes
Nov 26, 2024
benclifford
added a commit
that referenced
this pull request
Dec 3, 2024
The final use of channel errors was removed in PR #3690
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 3, 2024
The final use of channel errors was removed in PR #3690 This is part of #3515 channel removal project # Changed Behaviour Any user catching these errors explicitly will now get an error about the exceptions being undefined. Because these don't exist any more, it should be safe to remove those catches. ## Type of change - Code maintenance/cleanup
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 removes push/pull support from channels.
All the HPC providers used channel.push_file to push their batch scripts to the (no-longer) remote system. This has been a basically dead code path since removal of non-remote channels:
The channel is always a LocalChannel now (PR #3677)
The "remote" script directory is always the local script directory (PR #3688) and so
LocalChannel.push_filealways skips making a copy and returns the path it was given without further action.So all the removed code is a no-op, and this PR simplifies that into nothing.
Changed Behaviour
Some providers had an option to let users decide if scripts (and other files) would be pushed/pulled to the remote system. Those options are removed by this PR.
Type of change