You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand this is a bug report and questions should be posted in the Community Forum
I searched issues and couldn’t find anything (or linked relevant results below)
Steps to reproduce
I use tus-js-client with tus-server (upload To S3 (AWS, DigitalOcean)):
The downloads work fine, but since the last update, I systematically get a ‘red’ message in the nodejs console.
I used this version:
"@tus/s3-store": "^1.9.0",
"@tus/server": "^1.10.2",
Expected behavior
I have this message:
"Are you using a Stream of unknown length as the Body of a PutObject request? Consider using Upload instead from @aws-sdk/lib-storage."
Actual behavior
No warning message
The text was updated successfully, but these errors were encountered:
Hi, I think we can safely ignore this error as it's merely a hint that you can use their Upload class but that doesn't work for our purposes as we may get the body across multiple requests.
Initial checklist
Steps to reproduce
I use tus-js-client with tus-server (upload To S3 (AWS, DigitalOcean)):
The downloads work fine, but since the last update, I systematically get a ‘red’ message in the nodejs console.
I used this version:
"@tus/s3-store": "^1.9.0",
"@tus/server": "^1.10.2",
Expected behavior
I have this message:
"Are you using a Stream of unknown length as the Body of a PutObject request? Consider using Upload instead from @aws-sdk/lib-storage."
Actual behavior
No warning message
The text was updated successfully, but these errors were encountered: