mirror of
https://github.com/twisterarmy/twister-core.git
synced 2025-01-22 20:44:56 +00:00
too strict assert causes twisterd to abort when network goes down
This commit is contained in:
parent
22cba50e54
commit
80f389239b
@ -505,7 +505,10 @@ observer::~observer()
|
||||
// reported back to the traversal_algorithm as
|
||||
// well. If it wasn't sent, it cannot have been
|
||||
// reported back
|
||||
/* [MF] this assert seems too strict. Some usages of rpc_manager::invoke, for
|
||||
* example, don't test the return value (false) which indicates that packet was not sent.
|
||||
TORRENT_ASSERT(m_was_sent == bool(flags & flag_done) || m_was_abandoned);
|
||||
*/
|
||||
TORRENT_ASSERT(!m_in_constructor);
|
||||
#if defined TORRENT_DEBUG || TORRENT_RELEASE_ASSERTS
|
||||
TORRENT_ASSERT(m_in_use);
|
||||
|
Loading…
x
Reference in New Issue
Block a user