Error in writestream does not throw error

[chuyouchia]

Hi there, thanks for creating the node-client! I was implementing Authzed at work and was trying to get the experimental service's bulkImportRelationships to throw errors when it fails. Specifically, I was trying to throw an error while using a Writestream created using the client library v0.13.0.

^ In the callbacks I actually implemented callbacks in a bunch of places to try and get the error to appear.

However, it seems like these errors do not propagate (or thrown) up to the context where they have been called, even though the code execution managed to log the error. Screenshot attached below:

[chuyouchia]

I am not sure if I am using the library properly, would greatly appreciate any clarifications on this matter!

[tstirrat15]

I'm not sure if that's how callbacks typically handle errors. My sense is that when you're throwing the error, you're not throwing it in the parent context, but rather the execution context internal to the call. I think it's functionally similar to calling setTimeout(() => throw new Error('oops!')) in that it isn't in the control flow of the code that dispatched it.

What are you hoping to do with that error?