-
Notifications
You must be signed in to change notification settings - Fork 133
Fix: lint invalid ruleset panic #1689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1689 +/- ##
==========================================
- Coverage 28.24% 28.19% -0.06%
==========================================
Files 67 67
Lines 6949 6949
==========================================
- Hits 1963 1959 -4
- Misses 4845 4848 +3
- Partials 141 142 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
9000824 to
9b1492b
Compare
|
I need to drop this for a while. The next steps are to upgrade the tests to respect the new default rules for OAS |
9b1492b to
2fa46b0
Compare
769fb38 to
e205db9
Compare
Update on this - the output from linting doesn't seem to be deterministic anymore on v0.17, and there are issues with concurrency due to which tests are failing. Doesn't seem to be a quick fix. |
Fixes #1673, https://konghq.atlassian.net/browse/FTI-6730
Root cause: The version of vacuum module we used to lint did not append the rule to context if there were errors in validating the rule. This led to panic when we expected rule to be present later. This has been fixed in later releases.
Todo:
Verify that the version bump does not cause breaking changes