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

Record debugging information during perform, and report it when unexpected errors occur #26

Open
radix opened this issue Jan 1, 2015 · 1 comment

Comments

@radix
Copy link
Contributor

radix commented Jan 1, 2015

Similar to https://twistedmatrix.com/trac/ticket/6538 , which is for tracing callback history on Deferreds, I think we should have this feature for Effects.

I hope that it will be easier for Effects. At the very least, we don't have as much compatibility baggage to maintain as Deferred, but I think the referential transparency of Effects, and the fact that there are known fixed points when execution of Effects starts and ends, should make it much easier.

However, there's still some difficulty in reporting these traces to the user when an error occurs. Right now, we only give users an exc_info tuple, which provides no space for this extra debugging info. This is something that should be considered when working on resolving #24.

@radix radix changed the title Record debugging information during performance execution so it can be logged when unexpected errors occur Record debugging information during perform, and report it when unexpected errors occur Jan 1, 2015
@rbtcollins
Copy link
Contributor

You could attach the data to the exception. Also perhaps consider not doing this and instead using something like a Writer Monad to accumulate debugging information - which both user code and framework code could accumulate into.

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

No branches or pull requests

2 participants