Skip to content
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

[Data] Improve _resolve_paths_and_filesystem error message #38366

Merged
merged 2 commits into from
Aug 14, 2023

Conversation

bveeramani
Copy link
Member

Why are these changes needed?

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: Balaji Veeramani <[email protected]>
@bveeramani bveeramani merged commit 77f70e4 into master Aug 14, 2023
51 of 53 checks passed
@bveeramani bveeramani deleted the bveeramani/error-message branch August 14, 2023 18:09
@bveeramani bveeramani added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Aug 14, 2023
NripeshN pushed a commit to NripeshN/ray that referenced this pull request Aug 15, 2023
…ject#38366)

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

> paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

> 'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: NripeshN <[email protected]>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…ject#38366)

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

> paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

> 'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: harborn <[email protected]>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…ject#38366)

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

> paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

> 'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Signed-off-by: Balaji Veeramani <[email protected]>
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
…ject#38366)

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

> paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

> 'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: e428265 <[email protected]>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
…ject#38366)

If you pass an invalid input to _resolve_paths_and_filesystem, you get an error message telling you what types are valid, but it doesn't tell you what you passed it.

> paths must be a path string or a list of path strings.

This PR updates the error message to describe what you passed in:

> 'Expected paths to be a str, pathlib.Path, or list[str], but got None'

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: Victor <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants