-
-
Notifications
You must be signed in to change notification settings - Fork 211
Allow fallback to ARFF on ServerError and make explicit in warning #1272
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
Conversation
| source=cast(str, url), destination=output_file_path | ||
| ) | ||
| except (FileNotFoundError, urllib3.exceptions.MaxRetryError) as e: | ||
| except (FileNotFoundError, urllib3.exceptions.MaxRetryError, minio.error.ServerError) as e: |
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.
We could opt to catch all exceptions here instead. It would "future proof" in case new kinds of errors are raised, though generally it is useful to know what the errors are early and evaluate if different mitigation strategies are appropriate.
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.
I agree that we should make sure to see new error messages.
|
Note that unit tests are largely unaffected by the server issues (though not entirely) as the test server does not provide parquet urls so most tests simply work on ARFF only. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #1272 +/- ##
===========================================
- Coverage 85.26% 85.13% -0.13%
===========================================
Files 38 38
Lines 5104 5107 +3
===========================================
- Hits 4352 4348 -4
- Misses 752 759 +7
☔ View full report in Codecov by Sentry. |
mfeurer
left a comment
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.
This looks good to me. But how do we know that this will continue working when MinIO is up again?
| source=cast(str, url), destination=output_file_path | ||
| ) | ||
| except (FileNotFoundError, urllib3.exceptions.MaxRetryError) as e: | ||
| except (FileNotFoundError, urllib3.exceptions.MaxRetryError, minio.error.ServerError) as e: |
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.
I agree that we should make sure to see new error messages.
|
Not sure what you mean, all the changes do is provide a path when |
mfeurer
left a comment
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.
Thanks for the explanation. Now I get it, and this makes total sense to have.
How should this PR be tested?
Execute the following code snippet for a dataset not in your cache:
on
developit currently raises (due to server issues) onget_dataset:on this branch, it instead only issues a warning and falls back to
parquetarff: