api/matching endpoint chokes on large post request
@JonoYang is already working on this.
Since Nov 13, 2026.
Assessment
This issue has not been assessed yet.
Description
sending a scan of a large codebase as input to api/matching causes the server to time out processing the post request in the MatchingSerializer. This was not an issue before when we were using traefik to route traffic between purldb and matchcode.
- Dominant language
- HTML
- Stars
- 70
- Forks
- 76
- Avg merge
- 23m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from aboutcode-org/purldb
-
purlcli failsMay be free again @Anurag-S1ngh claimed this 18 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
aboutcode-org/purldb#891 · 2 comments ·
-
Incorrect set comparison between package names and PURLs in NPM sync logicPossibly taken @MuhammadBilal64 claimed this 45 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
aboutcode-org/purldb#890 · 1 comment ·
-
PypiVersionAPI.get_latest_date() crashes when a release entry is missing upload_time_iso_8601Possibly taken @drawliin claimed this 228 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aboutcode-org/purldb#863 ·
-
Add doctest and tests for clearcode coordinate helpersPossibly taken @drawliin claimed this 236 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aboutcode-org/purldb#861 ·
-
Preserve version ordering in packagedb VersionResponsePossibly taken @drawliin claimed this 237 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aboutcode-org/purldb#857 ·