Skip to content
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

Open
bordenbreejen opened this issue May 3, 2018 · 4 comments
Open

No response on execute #8

bordenbreejen opened this issue May 3, 2018 · 4 comments

Comments

@bordenbreejen
Copy link

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?

@FrostAndFlame
Copy link

@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.
#10

@coenvdwel
Copy link
Contributor

coenvdwel commented Oct 1, 2018

The .GetAwaiter().GetResult() is hideous and I think you should move the async all the way up the tree - the ExecuteAsync approach is a nice and safe alternative.

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?

@FrostAndFlame
Copy link

@coenvdwel Thanks for quick feedback on this!
Why .GetAwaiter().GetResult() is a bad idea -> https://stackoverflow.com/a/39007110
"This is most commonly seen when called on the UI thread or in an ASP.NET context (for pre-Core ASP.NET)."
I caught deadlock in ASP.NET context.

@coenvdwel
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants