Skip to content

Conversation

@harshadixit12
Copy link
Contributor

@harshadixit12 harshadixit12 commented Jul 4, 2025

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

@codecov-commenter
Copy link

codecov-commenter commented Jul 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 28.19%. Comparing base (ac5e383) to head (2fa46b0).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mheap mheap force-pushed the fix/lint-invalid-ruleset-panic branch from 9000824 to 9b1492b Compare July 29, 2025 12:11
@mheap
Copy link
Member

mheap commented Jul 29, 2025

I need to drop this for a while. The next steps are to upgrade the tests to respect the new default rules for OAS

@harshadixit12 harshadixit12 force-pushed the fix/lint-invalid-ruleset-panic branch from 769fb38 to e205db9 Compare August 4, 2025 04:04
@harshadixit12
Copy link
Contributor Author

I need to drop this for a while. The next steps are to upgrade the tests to respect the new default rules for OAS

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

lint command throwing SIGSEV error instead of outputting information on rule with bad syntax

4 participants