You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, a provenance resolved successfully to some fixed revision, but at a later point in time the host disappeared (e.g. svn.codehaus.org). In that case, the resolved provenance is retrieved from the database and passed to the scanner wrapper, but the scanner implementation will fail to download it. See e.g. this data
- provenance:
vcs_info:
type: "Subversion"
url: "https://svn.codehaus.org/plexus/plexus-containers"
revision: "981837"
path: ""
resolved_revision: "981837"
scanner:
name: "DOS"
version: "1.0"
configuration: ""
summary:
start_time: "2024-02-19T16:05:39.209930165Z"
end_time: "2024-02-19T16:05:39.266308013Z"
issues:
- timestamp: "2024-02-19T16:05:39.265568285Z"
source: "DOS"
message: "IOException: Unable to initialize a Subversion working tree in '/tmp/ort-DefaultWorkingTreeCache4990696171266543978'\
\ from https://svn.codehaus.org/plexus/plexus-containers.\nCaused by: SVNException:\
\ svn: E175002: unknown host\nsvn: E175002: OPTIONS request failed on '/plexus/plexus-containers'\n\
\ Caused by: UnknownHostException: svn.codehaus.org: Name or service\
\ not known"
severity: "ERROR"
In such a case it would be nice if the scanner implementation had a way to either trigger re-resolution of the provenance immediately, or at least delete the stored provenance to trigger re-resolution on the next run.
The text was updated successfully, but these errors were encountered:
Sometimes, a provenance resolved successfully to some fixed revision, but at a later point in time the host disappeared (e.g. svn.codehaus.org). In that case, the resolved provenance is retrieved from the database and passed to the scanner wrapper, but the scanner implementation will fail to download it. See e.g. this data
In such a case it would be nice if the scanner implementation had a way to either trigger re-resolution of the provenance immediately, or at least delete the stored provenance to trigger re-resolution on the next run.
The text was updated successfully, but these errors were encountered: