Autofixer 'update-lang-python' failed to register

[jankeromnes]

Bug description

When looking at the logs of the latest Autofix run, I noticed that our new custom fixer update-lang-python failed to register itself properly:

Failed to register fixer module update-lang-python.js Error: Command failed: pyenv update 2>&1 && pyenv install --list

�[2;32mUpdating /home/gitpod/.pyenv...
�[0mFrom https://github.com/pyenv/pyenv
 * branch              master     -> FETCH_HEAD
 * [new tag]           v2.2.5     -> v2.2.5
error: cannot lock ref 'refs/remotes/origin/master': is at f0f2cdd1c6b3b272168b508610cfbbe0ccef8ea5 but expected 44db3b03d0ca8e49e2fc25e3e582860a51ae0fc7
 ! 44db3b03..f0f2cdd1  master     -> origin/master  (unable to update local ref)
�[2;32mUpdating /home/gitpod/.pyenv/plugins/pyenv-doctor...
�[0mFrom https://github.com/pyenv/pyenv-doctor
 * branch            master     -> FETCH_HEAD
error: cannot lock ref 'refs/remotes/origin/master': is at 004fbacbaa94f7a545e3bf2acd13ee503b000a6e but expected 467d6d4e24eefa4d27b4cd11a3f2ceda4114124a
 ! 467d6d4..004fbac  master     -> origin/master  (unable to update local ref)
�[2;32mUpdating /home/gitpod/.pyenv/plugins/pyenv-installer...
�[0mFrom https://github.com/pyenv/pyenv-installer
 * branch            master     -> FETCH_HEAD
error: cannot lock ref 'refs/remotes/origin/master': is at 771de8e45459c5c40f148e4473c34a4d2fec7ee5 but expected 4164fced49af78c6275cb436c64369eb39c6acb1
 ! 4164fce..771de8e  master     -> origin/master  (unable to update local ref)
�[2;32mUpdating /home/gitpod/.pyenv/plugins/pyenv-update...
�[0mFrom https://github.com/pyenv/pyenv-update
 * branch            master     -> FETCH_HEAD
Already up to date.
�[2;32mUpdating /home/gitpod/.pyenv/plugins/pyenv-virtualenv...
�[0mFrom https://github.com/pyenv/pyenv-virtualenv
 * branch            master     -> FETCH_HEAD
Already up to date.
�[2;32mUpdating /home/gitpod/.pyenv/plugins/pyenv-which-ext...
�[0mFrom https://github.com/pyenv/pyenv-which-ext
 * branch            master     -> FETCH_HEAD
Already up to date.

I'm not quite sure what to make of this error. Maybe it's a temporary bug with pyenv itself?

Steps to reproduce

1. Check the latest Autofix logs in CircleCI (hint: you can click on the CircleCI readme badge in https://github.com/autofix-dev/cronjobs then simply log in with a GitHub account that is a member of our org)

Expected behavior

The fixer should register successfully and check for new fixes.

Example repository

No response

Anything else?

No response

[kylos101]

Scheduled (originally implemented here)