Open aalku opened 1 month ago
I was able to catch this exception by registering a listener for the error
event on the Firehose.
const firehose = new Firehose();
firehose.on("error", (e) => console.error(e));
According to Node's EventEmitter
specification, if there is no listener registered for the error
event, the event is thrown as an exception.
I hope this helps!
It does. Thenks! Also I want to say this here: In this other issue they told me that those errors come from another federated network. I think they are invalid messages or something, so we have to deal with possible invalid records in the network, I don't think there is a way to avoid it completely.
Maybe this tool should handle those errors differently?
https://github.com/bluesky-social/atproto/issues/2484#issuecomment-2108997630
Hello!! Thanks for your project.
I'm getting this error just for being subscribed to the firehose, as you can see the error is inside @atproto/repo module but I don't know if that depends on your code or not. Or maybe it even depends on my code, but I think it doesnt.
I'm just subscribed and this happens, and as it's not in my code I don't know how to catch it and I would need to restart node.
Can you give any help? Thanks!!!