8000 Errors should include a stack trace · Issue #16 · grailbio/reflow · GitHub
[go: up one dir, main page]

Skip to content

Errors should include a stack trace #16

Open

Description

@mariusae

Reflow isn't always very helpful when it errors. When execs fail, it provides a good deal of context, but other errors (e.g., stdlib errors, pattern matching errors, etc.) don't provide good context.

We should simply print a (Reflow) stack trace on every error, as this usually provides helpful context.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0