Improve package collection request queue logic #502
Assignees
Labels
enhancement
New feature or request
Comments
JonoYang
added a commit
that referenced
this issue
Jul 17, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
JonoYang
added a commit
that referenced
this issue
Jul 17, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
JonoYang
added a commit
that referenced
this issue
Jul 17, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
JonoYang
added a commit
that referenced
this issue
Jul 17, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
JonoYang
added a commit
that referenced
this issue
Jul 18, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
JonoYang
added a commit
that referenced
this issue
Jul 19, 2024
Signed-off-by: Jono Yang <jyang@nexb.com>
|
This has been merged into main |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good to set priority of when packages get collected/scanned depending on the input purl.
In the case where the user uses the
collectendpoint (GET /api/collect/?purl=pkg:npm/asdf@1.0.2), we would addpkg:npm/asdf@1.0.2to the top of the priority and scan queue. In the case of the/api/collect/index_packages/endpoint, the purls with exact versions will be at the top of the priority and scan queue. The purls that do not have versions specified will be added at the end of both queues and processed first-in first-out.The text was updated successfully, but these errors were encountered: