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
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.
The text was updated successfully, but these errors were encountered:
As reported here, stack traces reported by
wire/debug
may differ from those provided to the rejected promise returned bywire()
orcontext.wire()
. The only way this could happen, afaik, is if a differentError
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.The text was updated successfully, but these errors were encountered: