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
Since #739 has been merged, we now have the ability to redownload and save the package archive (**) after analysis.
It would be ideal if the downloaded/saved archive is the same one that's used for analysis
Some possible ways to achieve this:
Downloading the archive first in the worker container, then copying it into the static and dynamic sandboxes. These then do analysis as if on a local package.
Have the static analysis sandbox double as the 'package downloader' container, then copy the downloaded files back to the host and into the dynamic analysis container, as well as uploading them to the bucket
Have a separate 'downloader' container whose sole job is to download everything, and pass it to the other containers like in option 1.
** One caveat with all this is that Packagist packages hosted on GitLab don't offer direct package archive download URLs. We will need to figure out how to support this case (or possibly fall back to legacy behaviour).
The text was updated successfully, but these errors were encountered:
Since #739 has been merged, we now have the ability to redownload and save the package archive (**) after analysis.
It would be ideal if the downloaded/saved archive is the same one that's used for analysis
Some possible ways to achieve this:
** One caveat with all this is that Packagist packages hosted on GitLab don't offer direct package archive download URLs. We will need to figure out how to support this case (or possibly fall back to legacy behaviour).
The text was updated successfully, but these errors were encountered: