Skip to content
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

Multitool match-results-forward does not properly preserve conversion, taxonomies, or rules #1684

Closed
dbjorge opened this issue Sep 23, 2019 · 0 comments
Labels

Comments

@dbjorge
Copy link
Contributor

dbjorge commented Sep 23, 2019

Overview

While trying out the Multitool match-results-forward command in an attempt to document how to use it alongside axe-sarif-converter, we hit a variety of blocking issues that prevent us from being able to use it with our tool's sarif output.

The SARIF output files in the microsoft/axe-sarif-converter are the motivating examples; below, the repro steps use a more minimal repro file that demonstrate all the same issues we encountered.

Repro steps:

  • Download this repro SARIF file as repro.sarif
  • Run the following commands to produce output.sarif:
    dotnet tool install --global sarif.multitool --version 2.1.16
    sarif match-results-forward --previous ./repro.sarif ./repro.sarif --output-file-path ./output.sarif --pretty-print
    ...or, see output.sarif
  • Observe the following issues with output.sarif:
    • The original run's conversion section has been omitted
    • The original run's taxonomies section has been omitted
    • The original tool driver's rule at index 0 with id first-rule has been duplicated at index 2
    • The second result (which originally references the rule at index 1 with id second-rule) points to ruleIndex: 2, ruleId: 'second-rule', where ruleIndex 2 is actually the bogus copy of first-rule
@dbjorge dbjorge added the area-multitool Multitool command implementations label Sep 23, 2019
@ghost ghost self-assigned this Sep 25, 2019
@ghost ghost closed this as completed in 83ecf0f Sep 26, 2019
@ghost ghost added the resolved-fixed label Sep 26, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant