Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Recover channel moves from interruption and retries

未关闭
  • 哪里不对？
#429 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend, distributed-systems

调研方向

The payload names no files, so begin with the existing move flow described in #194 and #181, then read #375 for the progress reporting this builds on. This is design work: first decide what state an interrupted move leaves behind and whether it resumes or rolls back. Done means the three checklist items hold: the source stays usable, retries cannot create two active owners, and the UI reports the move state.

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

描述

Moves between this host and a hosted cell (#194, #181) work for idle channels with an exclusive cutover. What's missing is recovery when a move is interrupted: a crash, a lost reply, network loss, or the same command sent again during export, import or cutover.

  • A failed or interrupted move leaves the source usable, or offers a clear way to resume or roll back.
  • Retrying a move can never leave two active owners of the channel.
  • The UI says what state the move was left in (it builds on #375's progress).

Not in scope unless needed: moving busy channels, channels over 32 MiB, and moves across pi versions. Backup and restore is #178.

主要语言
TypeScript
星标
1
派生
0
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

githubnext/ace2 的其他 Issue

查看 githubnext/ace2 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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