call_runner doesn't report the signer sessions it opens
还没有人认领这个 Issue。
评估
调研方向
Start from call_runner and the LivePaymentSession class, where the signer sessions are opened and where auth_id would be read. The change is already in progress as eliteprox/livepeer-python-gateway#5 and needs re-submission against main, so check with maintainers before writing code. Read RunnerSelectionCursor too, since failover after a signed payment is a known limit tracked in #70. Done means the on_payment_session callback fires before each paid request, auth_id is returned from the State and state keys, and callers who omit the callback see no change.
由索引模型根据 Issue 内容生成。
描述
A caller of call_runner can't tell which signer sessions a call opened. That matters because the remote signer charges when it signs a payment, not when the runner delivers. A gateway that bills its users, or reconciles against Clearinghouse Batteries, has to link each charge to a call, including calls that failed after the payment was signed. The signer records each charge under the session's AuthID, but call_runner keeps its sessions private.
Proposed change
eliteprox/livepeer-python-gateway#5 adds two things:
call_runner(..., on_payment_session=callback)callscallback(session)for each session the signer signs, before the paid request is sent.LivePaymentSession.auth_idreturns that session'sAuthID. It reads go-livepeer'sStatekey and livepeer/node'sstatekey.
Callers that don't pass the callback see no change. The PR adds 17 tests, covering repeated 402s, a runner failure after payment, a refused session and a cancelled call.
It replaces #71, which was closed so the change could target the fork's releases/m2. That branch matches main, and GitHub reports no conflicts. Could it come back here as a PR against main?
Known limit
RunnerSelectionCursor still fails over after a signed payment, so one job can pay twice. #70 tracks that.
Why we need it
The Network Engineering SPE build track matches each job attempt to Batteries usage by auth_id. Until this is released, the build track pins the fork.
- 主要语言
- 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 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
livepeer/livepeer-python-gateway#70 · 2 条评论 ·
查看 livepeer/livepeer-python-gateway 的全部 Issue
相似的 Issue
-
Examples say cnx未关闭documentation embedded
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
Alishahryar1/free-claude-code#2111 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
namespace operations
难度 2/5 1-3 小时 新手友好度 72/100
EclipseFdn/open-vsx.org#14373 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复