Manipulating end of subscription event

[maksmachado]

Hello, I have some code that should only start when the entire subscription event is finished, so I placed this code inside the 'eose' event. However, I noticed that the 'eose' event, when using a relay pool, is being called more than once when there are relays with connection errors.
My question is if there is another way to wait for the end of the subscription event.

[fiatjaf]

I think this library is not flexible or powerful enough, you should try using https://github.com/nostr-dev-kit/ndk or https://www.npmjs.com/package/@snort/system instead.

[maksmachado]

I don't think that's it. I believe it's just me not knowing how to use the tool correctly, and I thought I could find the answers here, but I guess I was mistaken.
I did some more tests today, and the event "eose" triggered only once, even with connection errors. I really don't know if in my previous code I was calling the event more than once.

[Egge21M]

Please be aware that Pool will fake an EOSE event after 3400ms (or whenever specified), even if not all events have been received yet.