-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Ruby error in handle_composer_errors #1003
Comments
Still the case with version |
@mburumaxwell Still happening 😥 I've updated the original error in the first post with updated output |
I am facing the same issue. When try to update git submodules it shows
Any ideas how to solve it? |
Could this be related to #504 ? |
It worked fine in January and part of February (19th Feb may have been the last day it worked, so it may be something in 1.26.2 or 1.26.3 that caused it to fail?), though the linked issue is from February last year so may not be related? The immediate line before was checking is twig 3.8.0 should be updated, but the version resolver ruby file error (as included in the issue) is related to our ADO private repo not resolving (though nothing changed) |
If after today's version, this still occurs. I recommend confirming that the token has access to the second repository (sometimes things change without our knowledge). Should it persist beyond that, you would have to raise the issue at https://github.com/dependabot/dependabot-core because that's an implementation detail that I have no clue how to solve. We can keep this open for a few weeks until then. |
@mburumaxwell not sure if helps, but had a reply from someone dependabot/dependabot-core#9978 where it seems something needs fixing here
Not sure if the latest version fixed the issue as had issue last night/9 hours ago still with 1.36 |
@FinishingLine it was me 😄 My comment might have been a bit cryptic; what I was trying to say is that the authentication issues in TaskV1 have been fixed in this project if you upgrade to TaskV2, which handles private feed authentication more like the GitHub Dependabot does. If your pipeline is still failing, I'm going to assume your pipeline is still using version 1 of the task; Would you be able to try it with version 2 and see if it resolves the issue? If you still have auth issues, opening a new issue in this project would be helpful so we can investigate it with more relevant logs |
Describe the bug
A ruby error is being triggered when Dependabot is running since Monday and unable to fetch the git URL in Azure Repos (error suggests an authentication issue, but possibly also in part that our private repo has no version?)
Nothing has changed in our pipeline or dependabot files and token hasn't expired/revoked (but have tried regenerating anyway)
The text was updated successfully, but these errors were encountered: