Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Git issues during dependency updates
See original GitHub issue- This issue is blocking
- This issue is causing unreasonable pain
We’ve had some dependency update failures due to the nodes trying to access files in the git installation that are already in use by another process
Unexpected error processing action: The process cannot access the file 'D:\SvcFab_App\MaestroApplicationType_App0\temp\PullRequestActorServiceType\132639871000904417\git-portable\Git-2.22.0-64-bit.zip' because it is being used by another process.
Issue Analytics
- State:
- Created 2 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
Support issue dependencies #210
Dependency management of issues is not as easy as everyone makes it seem in this thread.
Read more >The Case Against Automatic Dependency Updates
First of all, automatic dependency updates do require mature delivery pipelines. It's no good automatically updating your dependencies if ...
Read more >Creating GitHub Issue Dependencies using ZenHub
Tracking dependency changes in the issue history. For all dependencies being added or removed events will be logged in the issue history for...
Read more >How to Update Dependencies Safely and Automatically ...
In this tutorial you'll learn how to use the Renovate app to check for dependency updates and then submit Pull Requests to update...
Read more >Group Dependabot Version Updates by Development or ...
If you are using the Dependabot grouped version updates feature (currently in public beta), you can now group your pull requests by dependency...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m fine with closing until it comes back. The 30th was a rollout day, so there might have been Service fabric-y things going on besides just the normal operations.
I also can’t see any evidence of this happening at all anymore. It happened for a single 90 second period on the 30th. The code all does the right thing, so this very much feels like something else was running on the machine and messing with our files. Like defender or just windows things.