-
Notifications
You must be signed in to change notification settings - Fork 14
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
Use full s3 URL for ConnectionTimeoutError #60
Use full s3 URL for ConnectionTimeoutError #60
Conversation
utils/s3_csv_reader.py
Outdated
try: | ||
df = pd.read_csv(filename.as_uri(), low_memory=False) | ||
except (botocore.exceptions.ConnectTimeoutError, botocore.exceptions.EndpointConnectionError): | ||
s3_filename = '/'.join(filename.parts[-2:]) |
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.
@dcjohnson24 This may be a dumb question, but why don't we try the f'https://{csrt.BUCKET_PUBLIC}.s3.us-east-2.amazonaws.com/{s3_...
approach the first time around if the pd.read_csv(filename.as_uri(), low_memory=False)
may throw an error?
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 catching this. You're right that it would probably work to just use the f'https://{csrt.BUCKET_PUBLIC}.s3.us-east-2.amazonaws.com/{s3_...
approach.
…t-workaround Use full s3 URL for ConnectionTimeoutError
Description
Line 235 of
compare_scheduled_and_rt.py
throws abotocore.exceptions.ConnectionTimeoutError
or abotocore.exceptions.EndpointConnectionError
. Using thes3
URL gets around this problem.Resolves #59
Type of change
How has this been tested?
Locally