XHR errors appear to come from Mimic - confusing (see attachment) about mimic

[adamkleingit]

What I mean is that it looks like there's a problem with BDSM.
Maybe we just need to wrap the error message with something that explains
that this is the actual result of the XHR

• Adam Klein http://il.linkedin.com/in/adamklein500
• CTO @ 500Tech.com http://500tech.com/ - Web and Mobile development
• hackademy.co.il http://hackademy.co.il/angularjs/about - AngularJS,
  Ruby on Rails training
• ([phone]

On Thu, Dec 17, 2015 at 11:34 PM, Maayan Glikser [email protected]
wrote:

Its related to JavaScript call stack. Hook is one of them.

On Thu, Dec 17, 2015, 23:26 Alex Ilyaev [email protected] wrote:

Is this related to the Hook library we're using?

—
Reply to this email directly or view it on GitHub
#105 (comment).

—
Reply to this email directly or view it on GitHub
#105 (comment).

[morsdyce]

What if you open the stack trace? In general xhr stack traces aren't very
helpful. You always see the last entry point for the xhr which is usually a
xhr library

[alexilyaev]

Is this related to the Hook library we're using?

[morsdyce]

Its related to JavaScript call stack. Hook is one of them.

[morsdyce]

Oh, I see. I think that's a great idea.

We should investigate this

[morsdyce]

This is a tricky one, in general we should look into capturing the stack trace when the request starts and throw that as the error when the request fails for 1 reason or another