Pipenv support triggers failure in renovate 38.39+

[sspans-sbp]

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.

GitLab and Renovate 38.39.6

Please tell us more about your question or problem

Renovate 38.39.6 is failing on repositories with a Pipfile.
Downgrading to 38.38.1 fixes it.

Probably related to #29000

Logs (if relevant)

Logs

INFO: Repository started (repository=596-sap-solman/playbooks)
"renovateVersion": "38.39.6"
ERROR: Repository has unknown error (repository=596-sap-solman/playbooks)
"err": {
"errno": -2,
"code": "ENOENT",
"syscall": "open",
"path": "/tmp/renovate/repos/gitlab/596-sap-solman/playbooks/Pipfile.lock",
"message": "ENOENT: no such file or directory, open '/tmp/renovate/repos/gitlab/596-sap-solman/playbooks/Pipfile.lock'",
"stack": "Error: ENOENT: no such file or directory, open '/tmp/renovate/repos/gitlab/596-sap-solman/playbooks/Pipfile.lock'"
}

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

Good luck,

The Renovate team

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[rarkins]

We need debug logs at a minimum, and ideally a reproduction repo.

Related PR: #29787

FYI @zharinov @nabeelsaabna

[zharinov]

Yes, without reproduction it's hard to tell

[nabeelsaabna]

hosted app still on 38.26.1 👍
should i hold the update ?

[rarkins]

@sspans-sbp are you still seeing this?

[nerrehmit]

I am seeing the same error in our internal repos with a Pipfile and created a minimal reproduction repo here: https://github.com/nerrehmit/renovate-debug

Here you can see the logs from the onboarding of renovate, which I merged and then two subsequent runs using the docker images 38.38 and 38.39: https://gist.github.com/nerrehmit/8db0fbfc360d3bef0e2501685d847f9b

Let me know if there is anything else I can do to help.

[zharinov]

What's strange is that file reads are wrapped in try-catch block and return null instead of throwing (in both Renovate and detect-tools codebases). That's why I'd like to see the reproduction, otherwise the source of this exception isn't clear to me.

[nerrehmit]

I think this is the source issue that has been reported over in the detect-tools repo:

• Pipenv manager seems to require .python-version file detect-tools#36