Missing incidents on the file after accepting resolution for one of the incidents

[savitharaghunathan]

I have three incidents in the file, one of which was triggered by a custom rule.

After resolving the following issue:

The sun.misc.BASE64Encoder class has been removed. It can be replaced with the Base64.Encoder class instantiated using the java.util.Base64.getMimeEncoder() method. For further examples on replacing BASE64Encoder with Base64.Encoder, refer to the "Code example" link below.

and accepting the resolution, the incident triggered by the custom rule is no longer listed after re-running the analysis.

When I stopped the server, deleted the logs folder, restarted the server, and re-ran the analysis, the custom rule violation reappeared.

Note: When I ran Kantra to verify locally, I could still see the incident triggered by the custom rule.

[savitharaghunathan]

custom rule link - https://github.com/savitharaghunathan/migrationex/blob/main/rules/rule.yaml
app link - https://github.com/savitharaghunathan/migrationex/tree/main

settings.json

{
    "konveyor.analysis.customRules": [
        "/Users/sraghuna/local_dev/rules"
    ],
    "konveyor.analysis.useDefaultRulesets": true,
    "konveyor.analysis.labelSelector": "(konveyor.io/target=jakarta-ee || konveyor.io/target=openjdk11 || konveyor.io/target=openjdk17) || (discovery)",
    "konveyor.kai.traceEnabled": true,
}

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[shawn-hurley]

I am moving this issue because the problem is in the java analyzer bundle filtering out a search match for the custom rule.

Going to dig in more tomorrow