-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No response on execute #8
Comments
@bordenbreejen I've found the root cause. That's because of .GetAwaiter().GetResult() inside ConfiguredServiceTransaction.Execute. I've created PR to add ExecuteAsync method. Hope this will help. |
The Although this is definitely better, I'm not really sure why the original version should block. We've moved on to our own fork, but this core method invocation is still there (and works as expected). Could you clarify on that, for my understanding? |
@coenvdwel Thanks for quick feedback on this! |
Thanks! Will fix this in our fork, too. We're not in a 'one-thread-at-the-time' context, that's why we're getting away with it, probably. But this is better in any way! |
I am trying to do a test payment with ideal, but after filling in all the fields you would normally fill in using the rest api, i get no response after calling execute. The thread seems to block somewhere. I have tried different issuers, different banks, but no luck so far. Does anyone maybe have an example or has something broken?
The text was updated successfully, but these errors were encountered: