Promise rejection value is a non-unwrappable cross-compartment wrapper.

[alanshaw]

I believe I've only seen this happen on Linux and not macOS. I use the reload extension link:

...and get the following errors:

I took out the module I'm using for TCP and I no longer get the error, so I originally thought it was something to do with trying to bind to the same port twice...but the errors above look like it comes from the service discovery code.

[Gozala]

@alanshaw unfortunately I don't get enough context from the description to tell which promise (returned by which function) is to blame. I did pin down one case that #71 addresses but I'm not sure if that is the same one.

If it still occurs with latest changes please reopen, if you are able to tell which API function is that promise from that would really help. I also suspect that error would still occur it's just it won't be an unwrappable wrapper. To fix the actual error we'll need preferable more isolated example that I can reproduce.

[alanshaw]

I didn't have a lot of time to put that issue together yesterday and consequently it wasn't as detailed as I'd liked. I'll try out the latest fixes and pin down the function causing the issue if it still exists. Thank you 👍