Queued fleet requests survive a gateway restart

未关闭
#1,637 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript

调研方向

The issue identifies the gateway's in-memory lease index, views, and fleet requests, but names no files or tests. Start by reading the gateway manual section describing this known gap and tracing where fleet requests are queued and dispatched. Decide which requests survive a restart and whether queue order is preserved; done means the agreed behavior is documented and waiting requests retain their required state across a gateway restart.

由索引模型根据 Issue 内容生成。

描述

feature:spec

Request: #945

Problem

A gateway restart loses every queued fleet request. The gateway's manual lists it as a known gap: "A fleet request is stored only once a worker takes it. A gateway restart loses every open request; ids answer 404, a repeated Idempotency-Key is new (maybe REQUESTER_ALREADY_LEASED)." The lease index, views and fleet requests live in memory only.

Who it is for

A fleet operator who restarts or updates the gateway while agents and CI jobs are waiting for a device. Every waiting caller loses its place and must ask again.

Open questions

  • Which requests survive: queued only, or also those dispatched to a worker but not yet granted?
  • Do they keep their place in the queue?

Written by an agent.

主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。