Skip to content

fix: honor rx schedule --limit 0 - #13

Closed
Pitchfork-and-Torch wants to merge 2 commits into
mainfrom
fix/rx-schedule-limit-zero
Closed

Pitchfork-and-Torch wants to merge 2 commits into
mainfrom
fix/rx-schedule-limit-zero

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown
Owner

Bug

build_schedule sliced passes with max(1, int(limit)), so skycache rx schedule --limit 0 still returned one slot instead of an empty list.

Distinct from prior cooks #5–#12 (integrity / DtnQueue / pack-freshness / handoff|gateway|rx field-log|dtn export --limit 0).

Fix

If limit <= 0, return no slots; otherwise slice to limit.

Test

  • PYTHONPATH=. python3 tests/test_rx_schedule_limit.py

…t, custody, USB mule v2, mesh hop-forward sim, not Starlink, not RFC 9171, not free commercial broadband.
build_schedule used max(1, limit), so --limit 0 still returned one pass slot.
Honor 0 as an empty slots list.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant