FilterKgraphTopNParameters.max_edges declares a maximum of 0.0 while defaulting to 50, so the published OpenAPI document fails validation against the OpenAPI 3.x schema:
50 is greater than the maximum of 0.0
Failed validating 'maximum' in schema:
{'type': 'integer', 'maximum': 0.0, 'title': 'Max Edges', 'default': 50}
The schema as served:
"max_edges": {"type": "integer", "maximum": 0.0, "title": "Max Edges", "default": 50}
at #/components/schemas/FilterKgraphTopNParameters/properties/max_edges. A maximum of 0.0 on a positive edge count looks like a le=0 where ge=0 (or no bound at all) was meant — as written, every permitted value including the default is invalid.
Affected (checked 2026-08-31): every deployment I can reach, in both flavours.
To reproduce:
import requests
from openapi_spec_validator import validate
validate(requests.get("https://nodenorm.transltr.io/openapi.json").json())
Found by test_openapi_json in TranslatorSRI/babel-validation, which validates each target's published document.
FilterKgraphTopNParameters.max_edgesdeclares amaximumof0.0while defaulting to50, so the published OpenAPI document fails validation against the OpenAPI 3.x schema:The schema as served:
at
#/components/schemas/FilterKgraphTopNParameters/properties/max_edges. Amaximumof0.0on a positive edge count looks like ale=0wherege=0(or no bound at all) was meant — as written, every permitted value including the default is invalid.Affected (checked 2026-08-31): every deployment I can reach, in both flavours.
To reproduce:
Found by
test_openapi_jsonin TranslatorSRI/babel-validation, which validates each target's published document.