John L.

Hi everyone - I wanted to update here that we haven't been able to replicate this error or identify any potential underlying cause on our SDK side. I personally have...

Hi @martinslota - thanks for reaching out. Before proceeding, I'd like to request your assistance in confirming that the issue persists when running the code against the actual AWS service...

Hi @fenos - this's interesting! I haven't been able to reproduce it on my end with S3 itself but haven't tested with MinIO. I'll have to dig deeper into it....

Appreciate the details. Please do share once you have more findings while I further look into it on my end.

Hi there - apologies for the long delay response. The `sendMessageBatch` operation in SQS can return a partial success response. This means that even if some messages in the batch...

Hi @sazarkin - thanks for reaching out. I'd like to understand what your workflow looks like, and how you're using SDK. In your code example, I see that you're client-dynamodb...

@sazarkin - the code you shared is incomplete. It doesn't show where API call is being made or which operation is being called. It only shows that you're importing the...

Thank you both for your suggestions, we'd have to review the options with the team and consider the option to improve this part of our docs. I'll keep this open...

Hi @jedwards1211 - thanks for reaching out. This was brought up to team discussion and as we all understand, this's because `archiver` doesn't accept standard valid `ReadableStream` type that's expected....

Thanks for your response. Totally understand the frustration that you're trying to help other users. However, since the type returned by `archiver` isn't standard to NodeJS, we can't make an...