SAVE failing to locate the file specified by artifactLocation
in the SARIF content
#489
Labels
bug
Something isn't working
artifactLocation
in the SARIF content
#489
TL;DR
The cause of the issue is that
artifactLocation
may be a path (an absolute or relative), and it can also be afile:
or anhttps://
URI, which we don't currently support, e.g.:A relative URI holding a relative path
A relative URI holding a relative path with a
uriBaseId
An absolute HTTPS URI
An absolute
file:
URI holding an absolute Windows pathCurrently, we don't support
file:
URIs.The issue equally affects both
save-0.3.6
andsave-0.3.7
.Non-goals
uriBaseId
is out of scope for this issue, see instead SARIF: add support for relative paths withuriBaseId
#490.file:
URI is encountered #491.Sample
save.toml
Test cases
Case 1: Windows,
artifactLocation
contains an absolutefile:
URI with an absolute pathExample:
Running
save --log all .
results in the following exception:Case 2: Windows,
artifactLocation
contains an absolutefile:
URI with a relative pathCase 3: Linux,
artifactLocation
contains an absolutefile:
URI with an absolute pathCase 4: Linux,
artifactLocation
contains an absolutefile:
URI with a relative pathThe text was updated successfully, but these errors were encountered: