Conversation
Collaborator
|
Hi @warthog9, I think you're the maintainer of the mirror. |
Contributor
|
re-ran the mirror and it popped in, if I had to guess some errant bit that caused an error somewhere. Not seeing anything in the logs so it might have been AWOL for a while. Double check it now. |
Collaborator
|
@EternalDreamer01, thanks for this PR, nice catch. Can you add a Moreover, can you add zlib to |
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Add playwright.download.prss.microsoft.com and cdn.playwright.dev in allowed-endpoints to fix the following failure when installing playwright: Downloading Chromium 143.0.7499.4 (playwright build v1200) from https://cdn.playwright.dev/dbazure/download/playwright/builds/chromium/1200/chromium-linux.zip (node:3714) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities. (Use `node --trace-deprecation ...` to show where the warning was created) Error: connect ECONNREFUSED 54.185.253.63:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '54.185.253.63', port: 443 } Also add v4.mirror.cveb.in:443 to fix the same kind of issue: ClientConnectorError: Cannot connect to host v4.mirror.cveb.in:443 ssl:default [Connect call failed ('54.185.253.63', 443)] All those issues are probably raised because ubuntu-latest is used instead of intel-ubuntu-latest since switch to ossf Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
https://nvd.nist.gov/vuln/detail/cve-2025-40939 has the following configurations: [{}] This will result in a crash as current code wrongly assumes that all configuration object has a nodes parameter Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Obviously, --import-json is mainly useful when db doesn't exist so drop
cvedb_orig.check_db_exists() from if statement
Moreover, do not exit after --import-json or --export-json to be
consistent with --import and --export
Finally, while at it, add --{im,ex}port-json to offline.md
Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com>
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
Signed-off-by: Dimitri Simon <dimitri.simon@telecom-sudparis.eu>
EternalDreamer01
force-pushed
the
fix/zlib
branch
from
3cebec4 to
b2f5c39
Compare
Collaborator
|
All tests passed, merging |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Zlib versions with a build number (4th element in version, like 1.3.0.1) was not managed.
Initially related to #5441