fix: [ISSUE] Issue while using API to extract text from documents (as a JSON response)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 718
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 23
Description
Describe the bug
A clear and concise description of what the bug is.
I tried to upload a document through the API, but I am getting an empty JSON response. (worked previously)
To reproduce
Steps to reproduce the behavior.
Should give a JSON response with all extracted details.
Expected behavior
A clear and concise description of what you expected to happen.
When I call the API by sending a document, I am not getting any response - It says "error: Non-JSON response"
Environment details
- Version: [e.g. 0.41.2]
Additional context
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem.
Contributor guide
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
Start by reproducing the API document upload described in the issue and inspect why the response is empty or reported as non-JSON. Compare the returned response with the expected JSON containing all extracted details; the issue provides no file or test entry point, so locating the relevant API path and coverage is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100