Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Clean up a moved channel's frozen copy at its hosting service

未關閉
#528 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
backend

研究方向

Start at the move paths for toLocal and toCompute, then trace channel deletion and the hosting service's frozen channel behavior; the issue gives no file or test names. Reproduce a move from a hosted channel, activate the destination, then delete the channel and check whether the frozen copy is removed or the failure is reported. Done means either expected cleanup path works and deletion cannot silently leave the copy behind.

由索引模型根據 Issue 內容生成。

描述

Found while building #499 and #500.

What happens

A move out of a hosting service (toLocal, or toCompute from a hosted channel since #522) freezes the channel at its service and keeps the frozen object there. Deleting the channel later doesn't remove that copy, and the service refuses a plain delete of a frozen channel. While testing, three such copies had to be unfrozen and deleted by hand.

Expected

  • Deleting a channel that once lived at a hosting service also removes its frozen copy there, or
  • the move removes the frozen copy once the destination has confirmed activation.

Either way, a delete that leaves a frozen copy behind should not fail silently.

Dogfooding: #5

主要語言
TypeScript
星號
1
分支
0
PR 合併指標
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 摘要。