-
Notifications
You must be signed in to change notification settings - Fork 573
Open
Description
While executing Digger in manual mode, get the error Failed to report project: unexpected status when reporting a project: 500
time=2026-02-12T11:54:14.327Z level=WARN msg="No orchestrator spec found (DIGGER_RUN_SPEC is empty); falling back to backendless mode. If this run was triggered by Digger backend, ensure your workflow passes 'with: digger-spec: ${{ inputs.spec }}' so DIGGER_RUN_SPEC is set."
time=2026-02-12T11:54:14.327Z level=INFO msg="Using GitHub (backendless)"
time=2026-02-12T11:54:14.327Z level=INFO msg="Initializing policy checker" hostname=http://localhost:8000 organisation=""
time=2026-02-12T11:54:14.328Z level=INFO msg="GitHub context parsed successfully"
time=2026-02-12T11:54:14.328Z level=INFO msg="loading digger configuration" workingDir=./ generateProjects=true changedFilesCount=0
time=2026-02-12T11:54:14.328Z level=INFO msg="loading digger config YAML" workingDir=./ generateProjects=true changedFilesCount=0
time=2026-02-12T11:54:14.328Z level=DEBUG msg="checking config file existence" ymlPath=digger.yml yamlPath=digger.yaml
time=2026-02-12T11:54:14.328Z level=DEBUG msg="file existence check" path=digger.yml exists=true
time=2026-02-12T11:54:14.328Z level=DEBUG msg="file does not exist" path=digger.yaml
time=2026-02-12T11:54:14.328Z level=INFO msg="using yml config file" path=digger.yml
time=2026-02-12T11:54:14.329Z level=DEBUG msg="reading digger config file" fileName=digger.yml
time=2026-02-12T11:54:14.329Z level=DEBUG msg="validating digger config YAML" fileName=digger.yml
time=2026-02-12T11:54:14.329Z level=DEBUG msg="digger config YAML validation successful" fileName=digger.yml
time=2026-02-12T11:54:14.329Z level=INFO msg="generating projects from config" fileName=digger.yml
time=2026-02-12T11:54:14.329Z level=INFO msg="successfully loaded digger config YAML" fileName=digger.yml projectCount=2 workflowCount=1
time=2026-02-12T11:54:14.329Z level=INFO msg="validating digger configuration" projectCount=2 workflowCount=1
time=2026-02-12T11:54:14.329Z level=DEBUG msg="validating projects configuration" projectCount=2
time=2026-02-12T11:54:14.329Z level=DEBUG msg="projects validation successful"
time=2026-02-12T11:54:14.329Z level=INFO msg="digger configuration validation successful"
time=2026-02-12T11:54:14.329Z level=INFO msg="digger configuration loaded successfully" projectCount=2 workflowCount=1
time=2026-02-12T11:54:14.329Z level=INFO msg="Digger digger_config read successfully"
time=2026-02-12T11:54:14.867Z level=ERROR msg="Failed to report project" projectName=layer1 error="unexpected status when reporting a project: 500"
time=2026-02-12T11:54:15.300Z level=ERROR msg="Failed to report project" projectName=layer2 error="unexpected status when reporting a project: 500"
I'm self-hosting the backend, using vLatest image.
- Function called from the CLI cli/pkg/github/github.go
- Implementation: libs/backendapi/diggerapi.go
When the backend receive the request :
I get the error error: ERROR: column "repo_id" does not exist (SQLSTATE 42703) from the /repos/{repository}/report-projects endpoint.
file: projects.go:476
Query: SELECT * FROM "projects" WHERE (name = 'layer1' AND organisation_id = 1 AND repo_id = 2) AND "projects"."deleted_at" IS NULL ORDER BY "projects"."id" LIMIT 1"
Related to #2074 ?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels