SSE 断开后，用户最关心的是内容有没有丢
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
长回复或沉浸式课程生成到一半，如果网络抖一下，前端最好别只是提示失败。用户会想知道任务还在不在、能不能继续、已经生成的部分会不会丢。这里可能需要 job id、partial response 保存，或者至少给一个明确的恢复提示。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the SSE response flow and how generated content is currently tracked; determine whether job identity, partial-response persistence, and recovery behavior exist. Done means the expected behavior after disconnection is specified and implemented, including whether users can resume and whether generated content is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100