-
Notifications
You must be signed in to change notification settings - Fork 60
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
Allow output_path to be a s3 path #83
Merged
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
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 17, 2021 18:40
47a3257
to
b2626df
Compare
katxiao
force-pushed
the
store-results-to-s3
branch
from
May 17, 2021 23:54
a55dd1f
to
ad700a9
Compare
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 17, 2021 23:54
b2626df
to
7ec0626
Compare
csala
suggested changes
May 18, 2021
sdgym/benchmark.py
Outdated
if output_path: | ||
scores.to_csv(output_path, index=False) | ||
|
||
_write_output_to_csv(scores, output_path, aws_key, aws_secret) |
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.
After comments from #77 are addressed this can become a one line change to write_csv(scores, output_path)
katxiao
force-pushed
the
store-results-to-s3
branch
from
May 18, 2021 18:22
ad700a9
to
39fd695
Compare
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 18, 2021 18:25
7ec0626
to
ab0d8aa
Compare
katxiao
force-pushed
the
store-results-to-s3
branch
from
May 18, 2021 18:27
39fd695
to
5c29ab0
Compare
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 18, 2021 18:27
ab0d8aa
to
a730077
Compare
katxiao
force-pushed
the
store-results-to-s3
branch
from
May 18, 2021 21:01
5c29ab0
to
9c5536c
Compare
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 18, 2021 21:01
a730077
to
bc28e15
Compare
katxiao
force-pushed
the
store-results-to-s3
branch
from
May 19, 2021 17:54
9c5536c
to
ea87801
Compare
katxiao
force-pushed
the
store-output-to-s3
branch
from
May 19, 2021 17:57
bc28e15
to
283780c
Compare
csala
approved these changes
May 19, 2021
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.
Looks good!
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.
If the user passes
output_path
as an s3_path (s3://<bucket-name>/path/to/dir
), the results are stored in the corresponding path of the given bucket. Ifaws_key
andaws_secret
are provided, they will be used to authenticate the s3 requests.✅ Ran with aws credentials and a private s3 bucket, and verified that the output file was uploaded.
Resolve #80