Runner selection: pool size, failure classification and payment_sent on rejections
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start with the proposal, then read RunnerSelectionCursor.next in src/livepeer_gateway/selection.py and discover_orchestrator_runners in src/livepeer_gateway/discovery.py. Trace the related reserve_session change from #37 and the still-open #36 before deciding the pool, ordering, failure categories, and payment state. Done means the requested selection and rejection information is defined and implemented consistently.
由索引模型根据 Issue 内容生成。
描述
The builder engine (proposal) will build its runner failover on runner_selector / RunnerSelectionCursor. Three things are missing for that.
Today (main at 44df061):
RunnerSelectionCursor.nexttries candidates in discovery order and moves on after any exception.- Its candidates come from
discover_orchestrator_runners, which returns the runners of the first batch of five orchestrators that has any. - There is no setting for how many candidates to consider, no ordering hook, and no way to tell a capacity refusal from other failures.
RunnerRejectionrecords only the URL and a reason string, so a caller cannot tell whether a failed attempt had already paid. With a session prepay, a start refused on capacity has paid.
Request:
- A maximum pool size, so selection can consider runners across more than one orchestrator batch.
- An ordering hook, or ranking inputs.
- A classified failure reason: capacity refusal versus unreachable versus other.
- Whether payment was sent, on each rejection.
Related: #37 forwarded orchestrators through reserve_session. That change is on main, but #36 is still open.
- 主要语言
- Python
- 星标
- 1
- 派生
- 8
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
livepeer/livepeer-python-gateway 的其他 Issue
-
call_runner rejects a top-level JSON array, so a runner cannot pass one through可能已有人在做 @rickstaa 于 61 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
livepeer/livepeer-python-gateway#64 · 1 条评论 ·
-
Align pricing terminology: pixels_per_unit -> pricing_unit_size (track go-livepeer #3942)可能重新可做 关联的 PR 已关闭且未合并。 未关闭Improvement
难度 1/5 1 小时以内 新手友好度 68/100
livepeer/livepeer-python-gateway#27 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
-
trickle_publisher: `_resolve_next_seq` fallback drops first video segment + logs noisy warning可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 1/5 1 小时以内 新手友好度 70/100
livepeer/livepeer-python-gateway#12 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 22/100
livepeer/livepeer-python-gateway#74 · 3 条评论 ·
查看 livepeer/livepeer-python-gateway 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#4025 ·
-
难度 2/5 1-3 小时 新手友好度 85/100
aws-samples/sample-per-model-bedrock#321 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 68/100
FavioVazquez/showtime#101 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
koush/ha_scrypted#81 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
google/osv-scanner-action#147 ·