Comment 5 for bug 1506358
Revision history for this message
| Daniel van Vugt (vanvugt) wrote Re: libmirclient gives up and exits prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit() | #5 |
Naively I would like to know; if there are "no new buffers" and if that's a blocker, then why is the client not just waiting for new buffers? Dying instead seems like an overreaction.