Closed fiatjaf closed 1 month ago
please take a look @mattn, is this the wrong approach?
Actually this has happened in the real world not because of a broken connection, but because @pablof7z was calling .QueryEvents()
manually and then not reading the returned channel until completion.
I still think it's a bug on this library to not handle that case correctly, but maybe we shouldn't fix and we should just say "beware: channels must be read until completion"?
I guess fixing is better if it's not incredibly inefficient.
This PR is so old I had forgotten about it. I think it's still applies, right?
LGTM
Thank you
this could happen in relay queries that exit before EOSE.
the channel inside
QueryEvents()
of every backend will just halt since no one is reading from it.