l3montree-dev / l3montree-dev/devguard

SCA on React repo throws Database Error

Open
#2,657 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug component/devguard-scanner
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

Running devguard-scanner sca in the CLI on a cloned repo of React throws a database error in the backend and ends the scan on a 500 Internal Server Error.

Backend log:

5:14PM ERR monitoring/alert.go:31 critical error encountered - not send to error tracking msg="Database error" error="extended protocol limited to 65535 parameters"

5:14PM ERR controllers/scan_controller.go:334 could not update sbom err="extended protocol limited to 65535 parameters\ncould not handle state diff\ngithub.com/l3montree-.......

5:14PM ERR middlewares/server.go:73 could not handle state diff: extended protocol limited to 65535 parameters method=POST path=http://host.docker.internal:8080/api/v2/scan/

The scan throws a 500 internal server error after SBOM enrichment suggestions:

3:14PM INF commands/sca.go:220 application component resolution enrichedBySupplementarySBOM=0 unresolved=14

Error: could not scan file: 500 Internal Server Error {"message":"Internal Server Error"}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by running devguard-scanner sca against a cloned React repository and review the logs around controllers/scan_controller.go:334 and commands/sca.go:220. Trace the SBOM update after enrichment suggestions, then verify that the scan completes without the PostgreSQL parameter-limit error or a 500 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.