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
{{ message }}
Repository navigation
Commit a3fe8ce
Browse filesBrowse the repository at this point in the historyBrowse files
Warn when a top-level cooldown duration can't be parsed
The cooldown library reads a duration it can't parse as 0, so a value
such as default: "1w" or "7 days" turned cooldown off without any sign
of it. Durations under cooldown.profiles were already rejected at
startup, but cooldown.default, cooldown.ecosystems, cooldown.packages
and cooldown.package_patterns were never checked.
The proxy now logs a warning at startup naming the value. It warns
rather than failing to start, so configs that start today keep
starting.
Durations support days (`7d`), hours (`48h`), and minutes (`30m`). Set to `0` to disable.
1278
+
Durations support days (`7d`), hours (`48h`), and minutes (`30m`). Set to `0` to disable. Other units such as weeks (`1w`) are not supported: a top-level value that can't be parsed applies no cooldown, so the proxy logs a warning at startup naming it. Invalid durations inside `cooldown.profiles` are rejected at startup.
1279
1279
1280
1280
Package PURL keys are normalized to canonical form before matching, so `pkg:npm/@babel/core` and `pkg:npm/%40babel/core` are equivalent, as are `pkg:pypi/Django` and `pkg:pypi/django`. If both forms configure the same package, the canonical entry wins.
warnings=append(warnings, "mirror.refresh without cache_metadata does not refresh Debian, Alpine or RPM packages: their indexes are found through the metadata cache")
0 commit comments