codecov[bot]
commented
11 months ago Codecov Report
Attention: 19 lines in your changes are missing coverage. Please review.
Comparison is base (
d5cdce4) 93.00% compared to head (7cc1a4e) 92.75%.:exclamation: Current head 7cc1a4e differs from pull request most recent head 14b7092. Consider uploading reports for the commit 14b7092 to get more accurate results
| Files | Patch % | Lines |
|---|---|---|
| RabbitMQ.Stream.Client/Reliable/Producer.cs | 56.66% | 9 Missing and 4 partials :warning: |
| RabbitMQ.Stream.Client/ClientExceptions.cs | 50.00% | 5 Missing and 1 partial :warning: |
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #337 +/- ## ========================================== - Coverage 93.00% 92.75% -0.25% ========================================== Files 115 116 +1 Lines 10845 10952 +107 Branches 878 893 +15 ========================================== + Hits 10086 10159 +73 - Misses 570 597 +27 - Partials 189 196 +7 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
The pr is part of https://github.com/rabbitmq/rabbitmq-stream-dotnet-client/issues/336 the aim is to standardise the behaviour.
Add AlreadyClosedException when a producer or super stream producer is closed In the same way like AMQP does with channels
Producer: Flush the pending messages when closed.
Producer: Add AlreadyClosedException when closed. So it is the same like: AMQP and RawProducer and RawSuperStreamProducer
Improve IsAKnownException function with the AggregateException that can contains known exceptions needed for reconnect the client
Add EntitiesStateTests to test all the status and verify that all the entities have the same behaviour