Closed marcbowes closed 7 months ago
cc @seanmonstar do we need to flush somehow prior to dropping? Or is this error benign?
I wrote a test using ReplayingConnection (near identical to the transcribe-streaming one) and the error doesn't show up there. However, my test fails because ..
thread 'test_success' panicked at 'assertion failed: `(left == right)`
left: `3`,
right: `4`: Frame count didn't match.
So, under test I have different behavior to what I captured (using RecordingConnection). I do not get the 'error writing a body' message under test.
This is a rather old issue and the sdk has gone GA since this issue was opened. Can you update to the latest version and see if you're still running into this problem?
Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.
Bug Report
As part of https://github.com/awslabs/amazon-qldb-driver-rust/pull/77/ I noticed that after I drop the send/receive channels of an eventstreaming connection I get an error logged. I'm not sure if this is doing any harm.
Version
This is a custom build (due to unreleased features) based off smithy-rs tag v0.27.0-alpha. I can try again using a newer version if that helps, but it requires a bunch of effort on my part :).
Platform
macOS.
AWS Services
QldbSessionV2 (unreleased)
Description
the following via tracing:
I think all of that is simply triggered by dropping the pairs:
https://github.com/awslabs/amazon-qldb-driver-rust/blob/ad2479b168efd8a768ffe71e88bdc40f00cedc01/amazon-qldb-driver/src/pool.rs#L67-L71