maziggy c0a50edbe8 fix(queue): re-check the queue quickly after a dispatch instead of always waiting 30s (issue #2555) ...

The scheduler slept a fixed 30s after every pass, so each printer that
freed up during a batch waited up to a full interval before its next job
was dispatched — on a farm, that idle gap stacked into the "several long
minutes" reporters saw between requesting prints and them starting (#2555).

check_queue() now reports whether it dispatched anything; run() loops again
after 3s on a productive pass and falls back to 30s otherwise. Fast ticks
only continue while the queue is actively draining, so this can't tight-loop:
a pass that dispatches nothing (all pending items behind busy printers, or a
wedged head-of-line job holding its printer) reverts to the normal interval.

2026-07-15 07:13:22 +02:00

..

_fixtures

…

integration

fix(cloud): stop reporting an expired Bambu Cloud sign-in as connected (issue #2562)

2026-07-14 11:29:56 +02:00

unit

fix(queue): re-check the queue quickly after a dispatch instead of always waiting 30s (issue #2555)

2026-07-15 07:13:22 +02:00

__init__.py

…

conftest.py

feat(sponsor-prompt): in-app toast at earned milestones

2026-06-20 15:50:58 +02:00

pytest.ini

…