Gitpulse
LatestReleasesStand-up
Merged
Size
S
Small: 10-100 weighted lines
Change Breakdown
Bug Fix70%
Maintenance30%
#3142fix: legacy master queue drain should never re-add entries

Legacy master queue strictly drains without re-adding entries

ER
ericallam
·Feb 27, 2026·#3142fix: legacy master queue drain should never re-add entries

The draining process for legacy master queues has been updated to strictly remove entries, ensuring a clean transition to the newer dispatch system.

The transition to the newer dispatch system can now proceed without legacy queues lingering indefinitely. The draining process for legacy master queues has been updated to strictly remove entries once processed. Previously, if a queue still contained messages during the drain phase, it was inadvertently placed back into the legacy tracking system. The handling queue updates now unconditionally removes the queue identifier from the legacy master queue, relying entirely on the V2 dispatch path for any new operations.

© 2026 · via Gitpulse