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

Investigate differing stack traces #105

Open
briancavalier opened this issue Jun 4, 2013 · 0 comments
Open

Investigate differing stack traces #105

briancavalier opened this issue Jun 4, 2013 · 0 comments

Comments

@briancavalier
Copy link
Member

As reported here, stack traces reported by wire/debug may differ from those provided to the rejected promise returned by wire() or context.wire(). The only way this could happen, afaik, is if a different Error object is being passed to plugin context listeners than is being used to reject the overall wiring promise.

Another possibility is that because wire/debug reports errors from within plugin infrastructure, and thus is being executed within promise nextTurn machinery, the stack somehow looks different, but isn't really ... or the way we're logging it makes it appear to be different.

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

No branches or pull requests

1 participant