External host error causing abort - skipping for repology data source despite explicit hostRules entry.
#38091
-
How are you running Renovate?A Mend.io-hosted app If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.No response Please tell us more about your question or problemI am constantly getting I have this config: {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:best-practices",
"security:openssf-scorecard",
":automergePr",
":automergeMinor",
":automergePatch",
":automergeDigest",
":automergeRequireAllStatusChecks",
":semanticCommits",
"npm:unpublishSafe",
"customManagers:dockerfileVersions",
"customManagers:githubActionsVersions"
],
"hostRules": [
{
"matchHost": "repology.org",
"abortOnError": false,
"maxRequestsPerSecond": 2,
"concurrentRequestLimit": 2,
"timeout": 180000
},
{
"enableHttp2": true
}
],
"prHourlyLimit": 2,
"prConcurrentLimit": 2,
"automergeSchedule": [
"* 0-7,18-23 * * 1-5",
"* * * * 0,6"
],
"schedule": [
"* 0-7,18-23 * * 1-5",
"* * * * 0,6"
],
"rebaseWhen": "automerging",
"minimumReleaseAge": "3 days",
"labels": [
// ...
],
"packageRules": [
// ...
],
"customManagers": [
// ...
]
}Despite explicitly setting repology to not abort on error (despite this being the default already according to the docs) I am no longer getting any PRs in my repo. I can confirm there are currently zero open Renovate PRs in my (private) repo. About 2 weeks ago Renovate was able to create PRs but it stopped doing so, so I have continually fine tuned the config like adding the hostRules for repology, to try to fix it. Logs (if relevant)LogsThis is from a run outside of the configured schedule, but I see the same kind of logs when running within the configured schedule during the night. |
Beta Was this translation helpful? Give feedback.
Answered by
RahulGautamSingh
Jul 1, 2026
Replies: 4 comments 1 reply
-
|
Any news on this issue? Did someone tried to use repology recently? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Confirming this still reproduces on Renovate 43.242.2 (Mend-hosted), July 2026, with repology.org intermittently returns The stack trace shows the error originating in Workaround that reliably stops the run-wide abort (at the cost of no updates for those packages): { "packageRules": [ { "matchDatasources": ["repology"], "enabled": false } ] }It would be great if repology's |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
For the record, I had spent some time last year investigated into this, without any success. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for looking into this folks. I debugged it locally and there seems to be a hardcoded logic to convert all errors to external host errors in repology datasource code which overrides the // lib/modules/datasource/repology/index.ts:230-241
} catch (err) {
if (err.message === HOST_DISABLED) { ... }
else { logger.warn(...); }
throw new ExternalHostError(err); // ← wraps EVERY error, always abortsI have created this issue to track that: #44329 PRs welcome addressing the bug. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Fix PR: #44326 |
Beta Was this translation helpful? Give feedback.
Answer selected by
RahulGautamSingh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for looking into this folks. I debugged it locally and there seems to be a hardcoded logic to convert all errors to external host errors in repology datasource code which overrides the
abortOnErrorsetting.I have created this issue to track that: #44329
PRs welcome addressing the bug.