Bug Report: 15 services use invalid gpu_backends values
Severity: High
Category: Manifest/Schema
Scope: resources/dev/extensions-library
Platform: All
Confidence: Confirmed
Branch: resources/dev — fix PRs must target resources/dev, NOT main
Description
14 services use gpu_backends: [none] but "none" is not a valid enum value — schema only allows amd, nvidia, apple, all. Additionally, gitea uses gpu_backends: [] which violates the minItems: 1 constraint. Any schema validator will reject these manifests.
Affected File(s)
Services using gpu_backends: [none] (14):
services/aider/manifest.yaml
services/baserow/manifest.yaml
services/chromadb/manifest.yaml
services/crewai/manifest.yaml
services/flowise/manifest.yaml
services/label-studio/manifest.yaml
services/langflow/manifest.yaml
services/librechat/manifest.yaml
services/milvus/manifest.yaml
services/open-interpreter/manifest.yaml
services/paperless-ngx/manifest.yaml
services/piper-audio/manifest.yaml
services/sillytavern/manifest.yaml
services/weaviate/manifest.yaml
Service using gpu_backends: [] (1):
services/gitea/manifest.yaml
Root Cause
Schema enum for gpu_backends does not include a "no GPU" option. Services that don't need a GPU used [none] or [] as workarounds.
Evidence
# 14 services:
gpu_backends: [none] # "none" not in enum [amd, nvidia, apple, all]
# gitea:
gpu_backends: [] # violates minItems: 1
Schema definition:
"gpu_backends": {
"type": "array",
"items": { "type": "string", "enum": ["amd", "nvidia", "apple", "all"] },
"minItems": 1
}
Reproduction
- Run any JSON schema validator against these manifest.yaml files
- Expected: valid
- Actual: validation error on gpu_backends
Impact
Schema validation fails for 15 out of 34 services. Automated tooling that validates manifests will flag nearly half the library as invalid.
Suggested Approach
For services that don't need a GPU, omit the gpu_backends field entirely. Alternatively, add "none" or "cpu" to the schema enum if there's a need to explicitly declare "no GPU required."
Bug Report: 15 services use invalid gpu_backends values
Severity: High
Category: Manifest/Schema
Scope: resources/dev/extensions-library
Platform: All
Confidence: Confirmed
Branch:
resources/dev— fix PRs must targetresources/dev, NOTmainDescription
14 services use
gpu_backends: [none]but"none"is not a valid enum value — schema only allowsamd,nvidia,apple,all. Additionally, gitea usesgpu_backends: []which violates theminItems: 1constraint. Any schema validator will reject these manifests.Affected File(s)
Services using
gpu_backends: [none](14):services/aider/manifest.yamlservices/baserow/manifest.yamlservices/chromadb/manifest.yamlservices/crewai/manifest.yamlservices/flowise/manifest.yamlservices/label-studio/manifest.yamlservices/langflow/manifest.yamlservices/librechat/manifest.yamlservices/milvus/manifest.yamlservices/open-interpreter/manifest.yamlservices/paperless-ngx/manifest.yamlservices/piper-audio/manifest.yamlservices/sillytavern/manifest.yamlservices/weaviate/manifest.yamlService using
gpu_backends: [](1):services/gitea/manifest.yamlRoot Cause
Schema enum for
gpu_backendsdoes not include a "no GPU" option. Services that don't need a GPU used[none]or[]as workarounds.Evidence
Schema definition:
Reproduction
Impact
Schema validation fails for 15 out of 34 services. Automated tooling that validates manifests will flag nearly half the library as invalid.
Suggested Approach
For services that don't need a GPU, omit the
gpu_backendsfield entirely. Alternatively, add"none"or"cpu"to the schema enum if there's a need to explicitly declare "no GPU required."