Closed bedzinsk closed 1 year ago
Without expertise in pip around, it may be difficult to tell whatis happening here. Could you offer a public repro in Azure DevOps?
Thank you for getting back on this issue! Unfortunately, that is private repo, which cannot be made public.
Is there a way to try to run it with older version of the plugin or older version of dependabot container/dependency? As I said it was working perfectly fine before, when it suddenly stopped: so to me it looks it is either extension, either dependebot packages.
A repro is a representation of the said issue to allow others reproduce similar behavior without exposing anything sensitive. Surely anyone can do this with a dummy organization, even a personal one. Others have done it here. Here are some samples: https://dev.azure.com/tingle/dependabot/_git with the matching builds at https://dev.azure.com/tingle/dependabot/_build
That said, running older versions can be done using the dockerImageTag
input. However, if you are going far behind, it may not work. It may be possibly to fix the task too but I haven't tried this, e.g - task: dependabot@1.10.0
Update on the issue:
rerun the pipeline today and I do not see the old error anymore, but a new one:
Checking if coverage 7.1.0 needs updating
🌍 --> GET https://pypi.org/simple/coverage/
🌍 <-- 200 https://pypi.org/simple/coverage/
🌍 --> GET https://pypi.org/simple/coverage/
🌍 <-- 200 https://pypi.org/simple/coverage/
/home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/python/lib/dependabot/python/update_checker/requirements_updater.rb:197:in `updated_requirement': Unexpected update strategy: auto (RuntimeError)
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/python/lib/dependabot/python/update_checker/requirements_updater.rb:38:in `block in updated_requirements'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/python/lib/dependabot/python/update_checker/requirements_updater.rb:33:in `map'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/python/lib/dependabot/python/update_checker/requirements_updater.rb:33:in `updated_requirements'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/python/lib/dependabot/python/update_checker.rb:78:in `updated_requirements'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/common/lib/dependabot/update_checkers/base.rb:269:in `preferred_version_resolvable_with_unlock?'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/common/lib/dependabot/update_checkers/base.rb:252:in `numeric_version_can_update?'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/common/lib/dependabot/update_checkers/base.rb:202:in `version_can_update?'
from /home/dependabot/dependabot-updater/vendor/ruby/3.1.0/bundler/gems/dependabot-core-f8c48ef2f569/common/lib/dependabot/update_checkers/base.rb:44:in `can_update?'
from bin/update-script.rb:583:in `block in <main>'
from bin/update-script.rb:533:in `each'
from bin/update-script.rb:533:in `<main>'
According to dependabot specs versioning-strategy
auto should be supported by pip:
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy
Maybe this should be an issue raised in the main repo at https://github.com/dependabot/dependabot-core ?
Thank you for your support! Apparently the setup is very sensitive to different dependabot versions. From my side issue can be closed.
About 5-10 days ago dependabot pipeline started failing for python packages, which have updated versions. There is no specific dependency which triggers this failure, basically any dependency update will result in similar stracktrace as below.
Stacktrace
.github/dependabot.yml