You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: