3 Commits

Include renames

Author	SHA1	Message	Date
dtourolle	abbb2d4770	fix: submitting to a stopped pool must be refused, not fatal ... ThreadPool::stop() ends with queues_.clear(), and submit() went straight to queues_[target] with no check. A submission arriving after stop indexed an empty vector and segfaulted. This is not a contrived teardown ordering. A node's space callback fires from whichever thread drained the channel, and that thread belongs to the *consumer*; the callback it runs belongs to the *producer*. Stop the producer first — which a sources-first shutdown does by design — and the consumer keeps draining its backlog, firing the producer's space callback into a pool that has already been torn down: ThreadPool::submit <- source node's space_callback <- Channel<int>::try_pop_now (relay draining its input) <- relay fire_once The static-network shutdown case in the next commit crashed about 12 runs in 20 on this. It survived until now because halt() stops in reverse topological order — consumers first — so the producer whose callback might fire is always still alive. shutdown() stops sources first and does not have that protection. Reading stopped_ without a lock would not fix it: the window between the read and the indexing is exactly where clear() runs. submit() takes a shared lock and stop() an exclusive one, so submissions still proceed in parallel with each other while being serialised against teardown. stop() sets the flag under the lock, releases it to join — a worker's task may itself call submit, and holding the lock across the join would deadlock against that — then retakes it to destroy the queues. Refusals are counted rather than silent. A teardown race is expected, but a node repeatedly trying to run after its pool is gone is worth being able to see. try_submit also checks stop_flag_ first, so a stopped node cannot claim the submit gate and leave it held. Not a smart-pointer problem, for anyone reading the crash: nothing here is owned by a raw pointer. It is std::vector::operator[] on a vector that was emptied by another thread. Verified in both directions: with the guard removed the new scheduler cases segfault; with it they pass.	2026-08-05 15:14:06 +02:00
dtourolle	7cb92a4091	Build docs with a pre-configured docker	2026-06-20 08:55:48 +02:00
dtourolle	f6bcaa15b0	Performance improvements, better readme and complete python bindings	2026-05-12 21:23:33 +02:00