Skip to content

fix: honor dtn export --limit 0 - #12

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

Pitchfork-and-Torch wants to merge 2 commits into
mainfrom
fix/dtn-export-limit-zero

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown
Owner

Bug

skycache dtn export --limit 0 used int(... or 50), so zero still exported up to 50 pending bundles. The web /api/dtn/export-mule path had the same coercion.

Distinct from prior cooks #5–#11 (integrity --record / disaster-drill render / DTN corrupt queue / pack-freshness sample limit / handoff export --limit 0 / gateway receipts --limit 0 / rx field-log --limit 0).

Fix

Honor limit=0 as an empty mule (do not coerce via or 50). None still defaults to 50.

Test

  • python3 -m pytest tests/test_dtn_export_limit.py -q

Pitchfork-and-Torch and others added 2 commits September 17, 2026 22:51
…t, custody, USB mule v2, mesh hop-forward sim, not Starlink, not RFC 9171, not free commercial broadband.
Stop coercing limit=0 to 50 via `or 50` in the CLI and /api/dtn/export-mule
path so an empty mule export is possible (same pattern as handoff/gateway/rx).
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