Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Managed channels currently rerank streams during generation even when Podium owns the intended order. This adds durable per-channel ordering ownership and
PUT /api/v1/channels/by-dispatcharr/{id}/external-orderfor core/plugin event and team channels, plus an explicit return-to-Teamarr control in the channel list.The endpoint validates full membership edits, commits ownership and recovery intent before the Dispatcharr write, confirms the live result, then finalizes positions, the order hash and memberships. Failed or interrupted writes remain fenced until an idempotent retry succeeds. Generation and reorder-only passes share a cross-process lock; the final stream-write boundary preserves surviving live order and appends new members across lifecycle, drift, pin and team/plugin paths.
Rollout requires Teamarr first, a shared database/lock directory across workers, and a single Teamarr manager for each Dispatcharr channel. Keep
PODIUM_TEAMARR_EXTERNAL_ORDERING=falseuntil Teamarr is deployed and smoke-tested. Unknown additions and disallowed windows return 422. Unmanaged acknowledgements are side-effect free; unmanaged adoption/remapping is operationally excluded during the direct-write handoff. Disabling Podium does not release stored ownership.Validation:
Bead: teamarr-76mo. Target: dev. Leave unmerged.