add stress tests and fix broken pipe when send too fast

[neonphog]

RESOLVES: #123

[neonphog]

lemme know if y'all are okay with this as an outside safeguard, or if it needs to be configurable

[jost-s]

This begs the question if there's something wrong with the channel, so to say? If the async method does not overflow it but the sync one does.

Is it a problem now that the channel doesn't get closed anymore if sending fails?

[neonphog]

This begs the question if there's something wrong with the channel, so to say? If the async method does not overflow it but the sync one does.

This is exactly the solution... because the async one will wait until there is space before pushing the new message on.

Is it a problem now that the channel doesn't get closed anymore if sending fails?

The channel does get closed on send failure. There's a match at the end of that function that does it.

[jost-s]

This is exactly the solution... because the async one will wait until there is space before pushing the new message on.

Okay, that wasn't obvious to me from the docs.

[ThetaSinner]

Yay for stress tests and this fix looks reasonable to me.

I think having some timeout is reasonable for now. It might give more context to require people making a network request to decide their own timeout but that's an adjustment we can make later if needed. It's good to have something in place for now