-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
ADO API responds with GitObjectDoesNotExistException when pushing file changes to branch #1413
Comments
@grixxie thanks for the report;
EDIT: Branch name is not the cause of the issue; tested below |
just a follow up to this; I've tried to reproduce your issue by doing the following:
All of these scenarios work without error; I was not able to reproduce the issue. Are you able to provide any more information that would help reproduce your issue? Can you identify what branch git commit |
Hi - thanks for the response. I also tested rerunning v2 with changes to the target branch name and ran into my same issue. To answer your question, I have no idea where that commit is coming from, I could not find it when I was doing my testing yesterday. I will be doing some more testing later today though so will let you know the outcome of that. You not being able to reproduce this issue definitely makes it seem like I'm doing something not quite right though... |
I have also just tried to use v2 for the first time and and running into this issue.
I also cannot find that commit ID at all, it must be one being created locally by Dependabot? I've ran the job multiple times and each time the The branch When running this, I have two package ecosystems. NuGet, which runs successfully, and then NPM, which fails. In my dependabot config file, I am attempting to use groups:
|
@rhyskoedijk I have found the same as @DaleMckeown post above; running the command |
If I flip the order of my package ecosystems to run NPM first and then NuGet, NPM runs successfully and NuGet errors instead. So it seems to be an issue related to processing multiple package ecosystems in the same Dependabot run. Also, removing the grouping configuration doesn't have any effect, the same error is thrown. Just tested again with the NPM config individually, and it works fine. So it's definitely related to having multiple package ecosystems in my case. |
Thanks @DaleMckeown, that is a good lead and something that I have not tested yet; I will investigate. |
This may be a good lead to find the root of the problem. However, just to point out my dependabot.yml config in the description of this issue, I'm only using a single package ecosystem (NuGet) and still running into this issue! |
Understood; At this point I'm just looking for a way to reproduce the error, even if it isn't your original scenario. I am out of ideas for now; If anybody is able to produce a minimal reproduction of their dependabot.yml and *.csproj that causes the error, I will revisit this. |
@rhyskoedijk I've scoured the logs again, not sure if this helps at all, but here is the first time the errant commit sha appears in the logs:
It then appears after finding the first package that needs an update. In my case, Quasar:
It then runs
It repeats the above for each NPM package that needs an update. It then marks the commit as processed, and outputs the changes detected:
It then outputs the create_pull_request response:
Then it errors:
|
I am facing the exact issue. My pipeline was successful on 14th October. The next execution on 21st October failed with this issue. I see a new version of this task has been released meanwhile. Successful pipeline
Failed pipeline
Update: |
Hi,
I am facing the following problem with my dependabot (v2) pipeline. My pipeline looks like so:
My dependabot.yml config looks like so:
My pipeline is erroring with the following error snippet, when it tries to call the /pushes endpoint of my repo via the ADO API to push the file changed. It is complaining that an object does not exist; I am not sure what this object is refering to. My
release-15
branch mentioned in my dependabot.yml definitely exists and is a different ID to the one mentioned in the error...The error:
Please advise if I am doing something wrong. If you need any more information then please let me know and I will provide. Thank you.
If anyone else is also experiencing this issue please respond!
The text was updated successfully, but these errors were encountered: