文档解析失败后，希望能保留失败原因
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
如果上传失败或抽取失败，刷新后最好还能在文档记录里看到失败原因。否则用户只记得“它失败了”，但不知道是格式、大小、扫描件还是后端错误。
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 or tests are named in the issue. Start by tracing the upload and extraction failure paths and where document records are persisted; done means that after a refresh, records show a useful failure reason for upload or extraction failures such as format, size, scanned-document, or backend errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100