mirror of
https://gitlab.com/d3tn/ud3tn.git
synced 2026-08-17 13:07:35 +02:00
89957b9e81
Previously, we were relying on a race condition for re-scheduling: if a suitable contact is ongoing, even if it is in the process of being dropped, it will be considered for re-scheduling a bundle. This explicitly ignores the contact being dropped. Due to the increased complexity, `_calc_bundle_schedule` is refactored slightly. Signed-off-by: Felix Walter <felix.walter@d3tn.com> |
||
|---|---|---|
| .. | ||
| aap | ||
| aap2 | ||
| storage_agent | ||
| __init__.py | ||
| config.py | ||