smithy connection was poisoned with latest aws_smithy_runtime

[WANG-lp]

Describe the bug

I encountered the error aws-smithy-runtime-api-1.6.1/src/client/connection.rs:24: smithy connection was poisoned when attempting to upload files to an object store (e.g., GCP and Aliyun; I haven't tested with AWS-S3) using the latest version of aws_smithy_runtime.

However, everything functions smoothly with aws-smithy-runtime version 1.4.0.

Any suggestions?

Expected Behavior

shouldn't have this issue

Current Behavior

error message: aws-smithy-runtime-api-1.6.1/src/client/connection.rs:24: smithy connection was poisoned

Reproduction Steps

Two APIs were used in my application:
head_object is used to check if an object already exists and then put_object is called to upload an object if there is no such object in the bucket.

Possible Solution

No response

Additional Information/Context

No response

Version

$ cargo tree | grep aws-
│   ├── aws-config v1.1.7
│   │   ├── aws-credential-types v1.2.0
│   │   │   ├── aws-smithy-async v1.2.1
│   │   │   ├── aws-smithy-runtime-api v1.6.1
│   │   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   │   ├── aws-smithy-types v1.1.10
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   ├── aws-runtime v1.2.2
│   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   ├── aws-sigv4 v1.2.1
│   │   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   │   ├── aws-smithy-eventstream v0.60.4
│   │   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   │   ├── aws-smithy-http v0.60.8
│   │   │   │   │   ├── aws-smithy-eventstream v0.60.4 (*)
│   │   │   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   ├── aws-smithy-eventstream v0.60.4 (*)
│   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-types v1.2.1
│   │   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   ├── aws-sdk-sso v1.25.0
│   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   ├── aws-runtime v1.2.2 (*)
│   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   ├── aws-smithy-json v0.60.7
│   │   │   │   └── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-smithy-runtime v1.5.3
│   │   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-types v1.2.1 (*)
│   │   ├── aws-sdk-ssooidc v1.26.0
│   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   ├── aws-runtime v1.2.2 (*)
│   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   ├── aws-smithy-json v0.60.7 (*)
│   │   │   ├── aws-smithy-runtime v1.5.3 (*)
│   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-types v1.2.1 (*)
│   │   ├── aws-sdk-sts v1.25.0
│   │   │   ├── aws-credential-types v1.2.0 (*)
│   │   │   ├── aws-runtime v1.2.2 (*)
│   │   │   ├── aws-smithy-async v1.2.1 (*)
│   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   ├── aws-smithy-json v0.60.7 (*)
│   │   │   ├── aws-smithy-query v0.60.7
│   │   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-smithy-runtime v1.5.3 (*)
│   │   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   │   ├── aws-smithy-xml v0.60.8
│   │   │   ├── aws-types v1.2.1 (*)
│   │   ├── aws-smithy-async v1.2.1 (*)
│   │   ├── aws-smithy-http v0.60.8 (*)
│   │   ├── aws-smithy-json v0.60.7 (*)
│   │   ├── aws-smithy-runtime v1.5.3 (*)
│   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   ├── aws-smithy-types v1.1.10 (*)
│   │   ├── aws-types v1.2.1 (*)
│   ├── aws-sdk-s3 v1.25.0
│   │   ├── aws-credential-types v1.2.0 (*)
│   │   ├── aws-runtime v1.2.2 (*)
│   │   ├── aws-sigv4 v1.2.1 (*)
│   │   ├── aws-smithy-async v1.2.1 (*)
│   │   ├── aws-smithy-checksums v0.60.8
│   │   │   ├── aws-smithy-http v0.60.8 (*)
│   │   │   ├── aws-smithy-types v1.1.10 (*)
│   │   ├── aws-smithy-eventstream v0.60.4 (*)
│   │   ├── aws-smithy-http v0.60.8 (*)
│   │   ├── aws-smithy-json v0.60.7 (*)
│   │   ├── aws-smithy-runtime v1.5.3 (*)
│   │   ├── aws-smithy-runtime-api v1.6.1 (*)
│   │   ├── aws-smithy-types v1.1.10 (*)
│   │   ├── aws-smithy-xml v0.60.8 (*)
│   │   ├── aws-types v1.2.1 (*)
│   ├── aws-smithy-runtime v1.5.3 (*)

Environment details (OS name and version, etc.)

Linux gcp 5.14.0-362.24.1.el9_3.cloud.0.6.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 13 15:08:34 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Logs

No response

[ysaito1001]

Hi @WANG-lp, thank you for filing this issue! Since you've mentioned the HeadObject operation, we are currently looking into likely relevant issues (this and this). Once the fix is out we will let you know, and you can try using that new version and see if we still observe any issues.

[ysaito1001]

We have just released a new version in the smithy-rs repository. Curious to know whether the issue can be resolved if you use the latest aws-smithy-runtime version 1.5.4.

[lapointexavier-pulse]

I can confirm it is fixed on my end going from 1.5.3 to 1.5.4

[WANG-lp]

Problem resolved. Thank you guys!

[WANG-lp]

I am closing this issue now. Thanks.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.