I should note that this fix only works for the latest version of aws.s3 - version 0.3.22. Users running off version 0.3.21 will have s3tools work as expected.
renv users now get the following error when trying to use the original s3tools::write_df_to_csv_in_s3 function
The below should resolve the issue. It looks like the issue has arisen due to amazon (or whoever is maintaing aws.s3) changing their aws.s3::put_object function, such that it now checks the file size of our rawConnection object and falls over.
I've also added in some quick regex to ensure the user enters a valid filepath. If you simply enter an s3 bucket name, you'll find a filepath of NA/entered_filepath when you browse to your S3 bucket.
I should note that this fix only works for the latest version of
aws.s3
- version 0.3.22. Users running off version 0.3.21 will have s3tools work as expected.renv users now get the following error when trying to use the original![Screenshot 2021-08-03 at 17 31 47](https://user-images.githubusercontent.com/45356472/128052441-da72e49c-b21d-48c3-8356-34a8eed8f167.png)
s3tools::write_df_to_csv_in_s3
functionThe below should resolve the issue. It looks like the issue has arisen due to amazon (or whoever is maintaing aws.s3) changing their
aws.s3::put_object
function, such that it now checks the file size of our rawConnection object and falls over.You can recreate this error using:
I've also added in some quick regex to ensure the user enters a valid filepath. If you simply enter an s3 bucket name, you'll find a filepath of
NA/entered_filepath
when you browse to your S3 bucket.