Skip to content

Filter internal instrumentation stacktrace items from SARIF #1382

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

Merged
merged 1 commit into from
Nov 17, 2022

Conversation

mmvpm
Copy link
Collaborator

@mmvpm mmvpm commented Nov 16, 2022

Description

Filtered out all items with className == "org.utbot.*" from the SARIF report stacktrace.

Now there is no org.utbot.instrumentation.process.HandlerClassesLoader.loadClass(ChildProcess.kt:48) in it:

image

Fixes #1366

Type of Change

  • Minor bug fix (non-breaking small changes)

How Has This Been Tested?

Automated Testing

org.utbot.sarif.SarifReportTest

Manual Scenario

Please, repeat the scenario from the issue #1366

Checklist:

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • The change contains enough commentaries, particularly in hard-to-understand areas
  • New documentation is provided or existed one is altered
  • No new warnings
  • All tests pass locally with my changes

@mmvpm mmvpm requested a review from SBOne-Kenobi November 16, 2022 09:59
@mmvpm mmvpm merged commit fc36ef8 into main Nov 17, 2022
@mmvpm mmvpm deleted the ideaseeker/filter_internal_calls_in_sarif_stacktrace branch November 17, 2022 07:46
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.

Unexpected internal calls in SARIF code flows
2 participants