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

Keep open chats alive across server restart

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
clojure
领域
backend

调研方向

The payload names no files or tests, so start from the issue's proposal: open chats should survive an ECA restart, with optional reopen of all chats or only the active one, and lazy reopening. Find where the server keeps chat state and how clients request or resume chats, then decide where persisted state should live. Done means a chat open before a restart can be resumed afterward and a prompt running at restart time is still interrupted. Check with a maintainer on the persistence design before writing code.

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

描述

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

Problem

I sometimes restart ECA to pick up updated env vars. After the restart, the chats that were open are closed and can't be used anymore, so I have to open a new chat and resume each one by hand.

Proposal

After a restart, the chats that were open before it come back, so I can keep working in them, in every client.

  • If several chats were open, reopen all of them (or only the active one, configurable).
  • Reopening could be lazy: the active chat right away, the others when first visited.
  • A prompt still running at restart time is interrupted, as today.
主要语言
Clojure
星标
1k
派生
82
平均合并
2 天 10 分钟
30 天内合并 PR
19

环境准备

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

从这里开始

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

editor-code-assistant/eca 的其他 Issue

查看 editor-code-assistant/eca 的全部 Issue

相似的 Issue

更多 Clojure Issue

把新 issue 发到你的邮箱

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