Closed ghost closed 4 years ago
Also has been issued here: https://github.com/stianeikeland/node-etcd/issues/88 and here: https://github.com/abbr/deasync/issues/91
Since this issue can only happen inside c code, and take has none, it is definitely a deasync issue. That tape triggers it is bad luck, but there’s nothing a JS lib can do to work around a flaw in something in native code.
Tape: 4.12.1 Node: 13.5.0
Tape is throwing v8 errors when using deasync. This is not the cause of deasync as it works outside of tape.
To reproduce:
This creates the error: