Marcel Märtens f3e4f022cb rather than letting the api/Participant handling the cleanup, we had to move over to the bParticipant::shutdownmanager. ... Because the old case didn't account for the Scheduler got dropped but Participant keept around. Shutdown behavior is quite easy now: bParticipant sends a oneshot, when that hits we stop. also when Participant gets droped we still stop as there woul dbe no sense in continue running the report_mgr ...		2022-06-30 22:14:24 +02:00
..
api.rs	rather than letting the api/Participant handling the cleanup, we had to move over to the bParticipant::shutdownmanager.	2022-06-30 22:14:24 +02:00
channel.rs	Add a new/unstable functionality report_channel.	2022-06-30 22:14:24 +02:00
lib.rs	Add a new/unstable functionality report_channel.	2022-06-30 22:14:24 +02:00
message.rs	extract protocol specific listen code from scheduler and move it to channel.rs	2021-04-29 17:51:52 +02:00
metrics.rs	fmt after applying clippy fixes after toolchain update	2021-07-12 12:09:27 +02:00
participant.rs	rather than letting the api/Participant handling the cleanup, we had to move over to the bParticipant::shutdownmanager.	2022-06-30 22:14:24 +02:00
scheduler.rs	Add a new/unstable functionality report_channel.	2022-06-30 22:14:24 +02:00
util.rs	fix logging cnt didnt reset	2021-06-27 22:51:23 +02:00