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

..

benches

protocoladdr change for listen and connect

2021-04-29 15:58:34 +02:00

examples

update a bunch of dependencies, including clap3

2022-04-04 11:43:29 +02:00

protocol

add a check to break the sending loop if the current bytes got greater than the total bytes.

2022-06-08 09:45:25 +02:00

src

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

tests

Add a new/unstable functionality report_channel.

2022-06-30 22:14:24 +02:00

Cargo.toml

update a bunch of dependencies, including clap3

2022-04-04 11:43:29 +02:00