Fix the nmdb CSV export by calling getvalue() #6064
Merged
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.
Not sure why this cropped up now, but along the way we lost the ability
to feed a file object to boto3 for uploading to S3. Boto creates a
hash of the content and expects bytes in making the hash, and
our previous routine delivered unicode.
The solution is to pass the bytes instead of the file object to boto,
by calling
getvalue()
on the file object.Testing
I ran the zusa prep job
cf.gov-nmdb-data-prep
against this branch, and it succeeded. The charts on DEV5 and CSV downloads on S3 look good.