[train] Fix trainer restoration from S3 #38251
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
Signed-off-by: Kai Fricke <kai@anyscale.com>
justinvyu
approved these changes
Aug 9, 2023
added 4 commits
August 9, 2023 23:32
shrekris-anyscale
pushed a commit
to shrekris-anyscale/ray
that referenced
this pull request
Aug 10, 2023
Currently failing with: ``` ValueError: Could not download from URI: URI `s3:/tune-cloud-tests/train-consistency/exp2/some_name/trainer.pkl` is not a valid or supported cloud target. Hint: Install s3fs to access S3 ``` The problem is that the restoration path is parsed as a local file path. This drops the second `/` in `s3://`, and this subsequently leads to a parse error in pyarrow. This doesn't seem to happen for e.g. the mock filesystem. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: Shreyas Krishnaswamy <shrekris@anyscale.com>
NripeshN
pushed a commit
to NripeshN/ray
that referenced
this pull request
Aug 15, 2023
Currently failing with: ``` ValueError: Could not download from URI: URI `s3:/tune-cloud-tests/train-consistency/exp2/some_name/trainer.pkl` is not a valid or supported cloud target. Hint: Install s3fs to access S3 ``` The problem is that the restoration path is parsed as a local file path. This drops the second `/` in `s3://`, and this subsequently leads to a parse error in pyarrow. This doesn't seem to happen for e.g. the mock filesystem. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: NripeshN <nn2012@hw.ac.uk>
arvind-chandra
pushed a commit
to lmco/ray
that referenced
this pull request
Aug 31, 2023
Currently failing with: ``` ValueError: Could not download from URI: URI `s3:/tune-cloud-tests/train-consistency/exp2/some_name/trainer.pkl` is not a valid or supported cloud target. Hint: Install s3fs to access S3 ``` The problem is that the restoration path is parsed as a local file path. This drops the second `/` in `s3://`, and this subsequently leads to a parse error in pyarrow. This doesn't seem to happen for e.g. the mock filesystem. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
vymao
pushed a commit
to vymao/ray
that referenced
this pull request
Oct 11, 2023
Currently failing with: ``` ValueError: Could not download from URI: URI `s3:/tune-cloud-tests/train-consistency/exp2/some_name/trainer.pkl` is not a valid or supported cloud target. Hint: Install s3fs to access S3 ``` The problem is that the restoration path is parsed as a local file path. This drops the second `/` in `s3://`, and this subsequently leads to a parse error in pyarrow. This doesn't seem to happen for e.g. the mock filesystem. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: Victor <vctr.y.m@example.com>
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.
Why are these changes needed?
Currently failing with:
The problem is that the restoration path is parsed as a local file path. This drops the second
/ins3://, and this subsequently leads to a parse error in pyarrow. This doesn't seem to happen for e.g. the mock filesystem.Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.