Skip to content

Why do errors have no stacktrace? #1364

Description

@adius

It's super annoying, that errors don't contain a stacktrace.

{ Error: ENOENT: no such file or directory, open '/repo_2017-09-01T1213/keywords'
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/repo_2017-09-01T1213/keywords' }

They contain absolutely no helpful information.
Is there a way to fix this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions