Help needed: regex manager produces hard-to-debug WARN: Error updating branch: update failure
#33821
Replies: 7 comments 2 replies
-
|
Hi there, We appreciate the effort you put into creating a reproduction. But your reproduction is not minimal yet, or is missing fields we ask for in our template. Please re-read the steps and documentation given in the previous message, and try again to create a minimal reproduction. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
Here is a minimal reproduction repo: https://github.com/DanySK/reproduction-renovate-bug-33821 |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
Hi @rarkins, thanks for your explanation, I very much appreciated it. I am sorry you got the feeling I am chasing or pushing you, I can grant you I am not. I am sorry if my phrasing sounded aggressive or insulting, it never wanted to be. I know it is a very edge case (not many people fiddle with custom regex managers), and I realize it requires debugging. Indeed, my badly phrased follow-up post was a request for existing methods (if any) to extract more information from the logs, with the goal of debugging autonomously. Thanks again, best. |
Beta Was this translation helpful? Give feedback.
-
|
I've also been hit by a "Value is not updated" I don't understand. Since there are several open discussions from recent weeks already -- I quickly found #26658 and #25272, there may be more -- I'll add the bare bones of my case here instead of creating yet another one. If that's not helpful, please advise. I'm on Bitbucket Server 8.19.13 with self-hosted Renovate 39.119.0 I have a Dockerfile like this: FROM docker-proxy.some.org/eclipse-temurin:21.0.5_11-jre-alpine-3.20@sha256:095e906b4ac20a3bd6a9f5afed00e62a457241ad711cd3569d7a5c9b567cfe57
# renovate: datasource=repology depName=alpine_3_20/libcrypto3 versioning=loose
ENV LIBCRYPTO_VERSION="3.3.2-r1"
RUN apk add --no-cache libcrypto3="${LIBCRYPTO_VERSION}"For context, tags with Alpine version like Since I was at it, I decided to tackle a bucket-list item of mine: bump the Renovate comments in the same PR. (cf. #24758, #29501). So I added this: {
customType: "regex",
fileMatch: [
"^Dockerfile.*",
],
matchStrings: [
"depName=(?<depName>alpine)_(?<currentValueSlug>[0-9_]+)",
],
datasourceTemplate: "docker",
versioningTemplate: "docker",
currentValueTemplate: "{{{ replace '_' '.' currentValueSlug }}}",
autoReplaceStringTemplate: "depName={{{ depName }}}_{{{ replace '.' '_' newValue }}}",
}I haven't used Lookup concludes without issue, far as I can tell. example snippet from the package update list{
"depName": "alpine",
"currentValue": "3.20",
"datasource": "docker",
"versioning": "docker",
"replaceString": "depName=alpine_3_20",
"updates": [
{
"bucket": "non-major",
"newVersion": "3.21",
"newValue": "3.21",
"newMajor": 3,
"newMinor": 21,
"newPatch": null,
"updateType": "minor",
"newDigest": "sha256:56fa17d2a7e7f168a043a2712e63aed1f8543aeafdcee47c58dcffe38ed51099",
"branchName": "renovate/alpine"
},
{
"isPinDigest": true,
"updateType": "pinDigest",
"newValue": "3.20",
"newDigest": "sha256:31687a2fdd021f85955bf2d0c2682e9c0949827560e1db546358ea094f740f12",
"branchName": "renovate/pin-dependencies"
}
],
"packageName": "alpine",
"warnings": [],
"sourceUrl": "https://github.com/alpinelinux/docker-alpine",
"registryUrl": "https://docker-proxy.some.org/",
"homepage": "https://hub.docker.com/_/alpine",
"currentVersion": "3.20",
"isSingleVersion": true,
"fixedVersion": "3.20"
}I'd have to add a rule to prevent the digest pin later, but that's fine for now. When creating branches, though, I get a whole slew of these: I don't know how to debug this any further, and I may just be holding it wrong. Note re "bad vibes": While this is related to my current for-pay work, I acknowledge that my client doesn't pay for support. So, no rush. I'm happy to provide a separate reproduction repo if my config snippet looks fine to you, but I wanted to hold off on that in case I made an obvious mistake. PS: Warm regards to your bosses at Mend; please give your employees paid time to engage on the issue tracker, thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @reitzig, I'm not sure whether it helps, but this seems to work instead: One thing I'm investigating now is this line in the log: the newline at the beginning looks suspicious to me |
Beta Was this translation helpful? Give feedback.
-
|
Update: I replaced the regex with I now get: It does not seem to be the culprit... |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
As a GitHub application, not self hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Not self-hosting.
Please tell us more about your question or problem
I created a regex manager:
{ "customType": "regex", "fileMatch": [ "^(workflow-templates|\\.github\\/workflows)\\/[^/]+\\.[Yy][Aa]?[Mm][Ll]$", "(^|\\/)action\\.[Yy][Aa]?[Mm][Ll]$" ], "matchStrings": [ "\\s+hugo-version:\\s+'?\"?(?<version>\\d+(\\.\\d+)*)'?\"?" ], "depNameTemplate": "hugo", "currentValueTemplate": "v{{{version}}}", "packageNameTemplate": "gohugoio/hugo", "datasourceTemplate": "github-tags", "versioningTemplate": "semver-coerced", "pinDigests": false }which seems to work correctly:
Except that it fails with a very hard to debug
(why did it fail? what's the problem?)
I guess something's wrong with my regex but I'm having a hard time understanding what. The repo where the bug emerged first is https://github.com/pslab-unibo/web-frontend.
The minimal reproduction is available at: https://github.com/DanySK/reproduction-renovate-bug-33821
Logs (if relevant)
the complete log is past the maximum allowed length for a GitHub post. I tried to extract the relevant part.
Logs
Beta Was this translation helpful? Give feedback.
All reactions