`Provided ruleset is not an object` error after upgrading from 1.37.12 to 1.37.13
@diatrcz arbeitet bereits daran.
Seit 13.7.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
We're seeing this error when trying to upgrade to the latest package:
iqp-service:openapi:validation: [ERROR] There was a problem with spectral.
iqp-service:openapi:validation: [ERROR] Provided ruleset is not an object
iqp-service:openapi:validation: [ERROR] Additional error details:
iqp-service:openapi:validation: [ERROR] RulesetValidationError: Provided ruleset is not an object
iqp-service:openapi:validation: at assertValidRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/validation/assertions.js:12:15)
iqp-service:openapi:validation: at new Ruleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/ruleset.js:35:44)
iqp-service:openapi:validation: at Spectral.setRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/spectral.js:66:73)
iqp-service:openapi:validation: at setup (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:160:12)
iqp-service:openapi:validation: at async runSpectral (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:34:20)
iqp-service:openapi:validation: at async runValidator (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/cli-validator/run-validator.js:234:17) {
iqp-service:openapi:validation: code: 'invalid-ruleset-definition',
iqp-service:openapi:validation: path: []
iqp-service:openapi:validation: }
device-service:openapi:validation: [ERROR] There was a problem with spectral.
device-service:openapi:validation: [ERROR] Provided ruleset is not an object
device-service:openapi:validation: [ERROR] Additional error details:
device-service:openapi:validation: [ERROR] RulesetValidationError: Provided ruleset is not an object
device-service:openapi:validation: at assertValidRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/validation/assertions.js:12:15)
device-service:openapi:validation: at new Ruleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/ruleset/ruleset.js:35:44)
device-service:openapi:validation: at Spectral.setRuleset (/workspace/app/device-management/node_modules/ibm-openapi-validator/node_modules/@stoplight/spectral-core/dist/spectral.js:66:73)
device-service:openapi:validation: at setup (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:160:12)
device-service:openapi:validation: at async runSpectral (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/spectral/index.js:34:20)
device-service:openapi:validation: at async runValidator (/workspace/app/device-management/node_modules/ibm-openapi-validator/src/cli-validator/run-validator.js:234:17) {
device-service:openapi:validation: code: 'invalid-ruleset-definition',
device-service:openapi:validation: path: []
device-service:openapi:validation: }
We run the tool like this:
lint-openapi -s --impact-score -r .spectral.yml -w 370 src/modules/openapi/openapi-spec.json
Here is the .spectral.yml in this case:
extends: '@ibm-cloud/openapi-ruleset'
rules:
ibm-enum-casing-convention: warn
ibm-required-array-properties-in-response: warn
# GET /workloads returns a usage status, this is not returned for sessions or legacy jobs (old pricing model)
# added as a warning to unblock us for now but we should try to resolve this
ibm-required-enum-properties-in-response: warn
- Vorherrschende Sprache
- JavaScript
- Sterne
- 635
- Forks
- 98
- Ø Merge
- 1 T. 5 Std.
- Gemergte PRs (30 T.)
- 8
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus IBM/openapi-validator
-
security
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 52/100
IBM/openapi-validator#875 · 1 Kommentar ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 45/100
IBM/openapi-validator#748 · 4 Kommentare ·
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 42/100
IBM/openapi-validator#747 · 2 Kommentare · 1 Reaktion ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 32/100
IBM/openapi-validator#643 · 3 Kommentare ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
IBM/openapi-validator#545 · 1 Kommentar ·
Alle Issues in IBM/openapi-validator
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
jonathanong/no-mistakes#3332 ·
Maintainer antworten meist innerhalb von 1 Tag
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
githubnext/gh-aw-workshop#5674 ·
Maintainer antworten meist innerhalb von 1 Tag
-
更新已收录主题套装为三主题及管理器兼容说明Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 62/100
awesome-dsh-plugin/awesome-dsh-plugin#14970 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
swc-project/swc-ai-issues#653 ·