@petkaantonov I don't think this duplicate of the issue #9. That issue seems to be about an error thrown inside asynchronous (setTimeout) code executed inside a Promise.
My issue is about the runaway Promise warning not including a long stack trace. When the runaway Promise originates from fromCallback(). If it originated from a different method, it would work. I think this may be related to #871. And I do not believe this would require domains, AsyncListener, or similar to solve.