Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

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

Copy link
Copy link
@radix

Description

@radix
Issue body actions

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.