Original call to async.series cannot be traced

[boutell]

longjohn is awesome, but for some reason, it can't quite finish the job of tracing from one of the various steps in an async.series call (using the well-known async npm module) all the way back up to the place where async.series was invoked.

I have put together a simple test showing that the trace reaches a line of code in async.series itself, where it invokes async.mapSeries, but never rises above that to the application code that actually invoked async.series.

I am scratching my head here because I don't see where anything fancy is happening up to that point in the async.series code that would make it tough to retain the rest of the stack trace above that point.

I would love some insight as to what keeps longjohn from reporting the whole story.

Thanks!

https://github.com/boutell/longjohn-async-test

[mattinsler]

I can replicate this, but am having a hard time figuring out what is cutting the stack list off. I'll continue to look into this. It's seems to be an edge case within longjohn and not something directly related to async.

[boutell]

Thanks for checking it out!