A few errors
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 121
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 1
Description
Trying to search a collection
Search Error
{"error":"Failed to search collection: nResults must be \u003c= the number of documents in the collection"}
error= latency=437148047 latency_human=437.148047ms bytes_in=33 bytes_out=108
Unsupported file type will still get uploaded
ERROR msg=Unsupported file type: .sh={"Key":"source","Value":{}}
ERROR msg=Failed to store file !BADKEY=failed to store file: not implemented source={"filename":"/app/routes.go","lineno":235}
Stuck on "upload" but uploads the file
status=500 error= latency=711817 latency_human=711.817µs bytes_in=7728 bytes_out=72
No https?
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
Start by reproducing the collection search and file-upload failures described in the issue, then inspect the upload path around routes.go:235 and the related search entry point. Done means the reported search, unsupported-file, and stuck-upload errors no longer occur and the HTTPS question has a documented answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100