Open nesherhh opened 10 months ago
Ah, I see. Half of the closed issues pertain to this deadlock. Is this project still active?
Hi, Yes, it's active, Contact me on our slack channel
On Tue, Jan 9, 2024, 10:04 Daniels Danilins @.***> wrote:
Ah, I see. Half of the closed issues pertain to this deadlock. Is this project still active?
— Reply to this email directly, view it on GitHub https://github.com/kubemq-io/kubemq-CSharp/issues/30#issuecomment-1882577997, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK5WGXAXLVY3CG4LLOE7EALYNT22HAVCNFSM6AAAAABBSELWLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSGU3TOOJZG4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Due to the extensive use of
.Wait()
and.Result
in Transaction.cs, I am encountering deadlocks. The methods — Receive, AckMessage, RejectMessage, ExtendVisibility, Resend, and Modify — are currently implemented as "Sync over Async." They should all be asynchronous and return a Task.