Dependabot job stuck in queued after FileUpdater failed error
Is there an existing issue for this?
- [X] I have searched the existing issues
Package ecosystem
nuget
Package manager version
No response
Language version
dotnet6.0
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
updates:
- package-ecosystem: "nuget"
directory: "/"
schedule:
interval: "daily"
allow:
- dependency-name: "cx-*"
registries:
- nuget-org
- gh-packages
groups:
cx-group:
patterns:
- "cx-*"
registries:
nuget-org:
type: "nuget-feed"
url: "https://api.nuget.org/v3/index.json"
gh-packages:
type: "nuget-feed"
url: "https://nuget.pkg.github.com/firecatapult/index.json"
username: "x-access-token"
password: "${{ secrets.GH_PACKAGES_PAT }}"
Updated dependency
No response
What you expected to see, versus what you actually saw
Expected:
- job completes successfully after opening a PR. Job/action is then in a completed state, or if not then a warning state due to encountered errors
- Subsequent job starts on scheduled
- New job can be started manually by kicking the action
Actual:
- Job restarted into a queued state after hitting a FileUpdater error
- Queued job can't be cancelled with the cancel button
- New job can't be started
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
No response
I have a similar issue that dependabot stuck with Queued status about 2 weeks!!!
@jakecoffman Can I pull you in to this one? I don't see anything specific to NuGet that would leave the jobs stuck in a queued state.
I hit this one yesterday too and my build is still stuck. No new ones will queue up while this one is in the Queued state
Happens the same to me! Is there any solution for this? It's very annoying to have dependabot jobs stuck in queued state...
Any updates or maybe workarounds? I am facing same issue and I can't even cancel the queue-ed dependabot job...
I'm facing same issue and my flows are just stuck with no errors for hours Is there a bug into the usage of daily interval?
+1 pip update job timed out - tried to rerun and is stuck queued and I can't cancel it because it "failed to cancel workflow"