Closed BojanPantovic1989 closed 4 years ago
@Falco20019 I wasn't able to test using 0.4.1, but I applied changes to make everything async.
Looks great to me! Looks like maybe something went wrong the continuous integration above but I had written test cases for the original fix. If those still pass, I'm happy.
Thanks!
The CI failed because there were some deprecation warnings (treated as errors) from NuGET. I just fixed them. I will rerun the CI.
@BojanPantovic1989 Can you please fix the DCO? Click on the "Details" link to get instructions for it.
Hi @Falco20019 it should be fixed now.
I'm testing it a bit more right now. I found that current 0.4.1
has problems if something on the sender goes wrong. Since we use command.ExecuteAsync().Wait();
, this will throw an AggregateException
instead of SenderException
. This PR should fix it since it's using async/await again.
Do not publish the version ?? We have a problem with version 0.4.1
@EngRajabi Sorry, I missed that this is still open. I will release it now.
@Falco20019 thanks
Which problem is this PR solving?
-Fixes #189
Short description of the changes