Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cleanupHttpCache: invalid cache data warning #28440

Closed
rarkins opened this issue Apr 16, 2024 Discussed in #28432 · 5 comments · Fixed by #28441 or #28447
Closed

cleanupHttpCache: invalid cache data warning #28440

rarkins opened this issue Apr 16, 2024 Discussed in #28432 · 5 comments · Fixed by #28441 or #28447
Assignees
Labels
help wanted Help is needed or welcomed on this issue priority-1-critical A bad bug or work that is holding up a lot of other important features or fixes status:in-progress Someone is working on implementation type:bug Bug fix of existing functionality

Comments

@rarkins
Copy link
Collaborator

rarkins commented Apr 16, 2024

Discussed in #28432

Originally posted by amezin April 16, 2024

What would you like help with?

I think I found a bug

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Bitbucket Server, Docker image ghcr.io/renovatebot/renovate:37.296.0-full

Please tell us more about your question or problem

Since a recent update I'm getting "cleanupHttpCache: invalid cache data":

  • once for every repository if RENOVATE_REPOSITORY_CACHE=enabled

  • twice if RENOVATE_REPOSITORY_CACHE=reset

  • no warnings if RENOVATE_REPOSITORY_CACHE=disabled

Removing all directories doesn't seem to help.

Logs (if relevant)

Logs
DEBUG: validateReconfigureBranch() (repository=TEST/repo)

DEBUG: No reconfigure branch found (repository=TEST/repo)

 WARN: cleanupHttpCache: invalid cache data (repository=TEST/repo)

DEBUG: Removing any stale branches (repository=TEST/repo)

DEBUG: config.repoIsOnboarded=true (repository=TEST/repo)
@rarkins rarkins added type:bug Bug fix of existing functionality priority-1-critical A bad bug or work that is holding up a lot of other important features or fixes labels Apr 16, 2024
@rarkins rarkins pinned this issue Apr 16, 2024
@rarkins
Copy link
Collaborator Author

rarkins commented Apr 16, 2024

Workaround: downgrade, or use https://docs.renovatebot.com/configuration-options/#loglevelremap to remap it to debug or trace and ignore

@rarkins rarkins self-assigned this Apr 16, 2024
@rarkins rarkins added the status:in-progress Someone is working on implementation label Apr 16, 2024
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 37.301.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@amezin
Copy link
Contributor

amezin commented Apr 16, 2024

I still see the same warning with ghcr.io/renovatebot/renovate:37.301.4-full

@rarkins rarkins reopened this Apr 16, 2024
@rarkins
Copy link
Collaborator Author

rarkins commented Apr 16, 2024

Needs someone with one of the affected platforms handy to debug/test

@rarkins rarkins added the help wanted Help is needed or welcomed on this issue label Apr 16, 2024
@rarkins rarkins assigned zharinov and unassigned rarkins Apr 16, 2024
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 37.301.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@rarkins rarkins unpinned this issue Apr 19, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Help is needed or welcomed on this issue priority-1-critical A bad bug or work that is holding up a lot of other important features or fixes status:in-progress Someone is working on implementation type:bug Bug fix of existing functionality
Projects
None yet
4 participants