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

Long retry delays may be bypassing mask and allowing further async exceptions to leak beyond recovering #49

Open
ozataman opened this issue Jun 21, 2017 · 1 comment

Comments

@ozataman
Copy link
Member

ozataman commented Jun 21, 2017

Seeing some behavior that suggests the mask approach in recovering is not blocking "interruptible" actions, including perhaps threadDelay, therefore allowing a repeat async exception while the retry block is waiting to go un-caught and leak outside of the recovering block.

What to do here? It is probably not prudent to use uninterruptibleMask as explained in Control.Exception docs.

@MichaelXavier
Copy link
Contributor

I don't feel super confident in my understanding of masking exceptions to weigh in here. I know that Michael Snoyman and Roman Cheplyaka have done blog posts in this area and may have more informed opinions. Wonder if it would be okay to reach out to them?

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

2 participants