starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Guidance: git submodule update --init --recursive (Resource temporarily unavailable) #1682

New Issue
Closed
opened 2026-01-30 22:33:43 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 22:33:43 +00:00
Owner
Copy Link

Originally created by @phfbfc on GitHub (Jun 14, 2019).

Followed README and build instructions from issue 489.
Got stuck at:
git submodule update --init --recursive
Which yielded:
0 [main] sh 6324 fork: child 1504 - died waiting for dll loading, errno 11
/mingw64/libexec/git-core/git-sh-setup: fork: retry: resource temporarily unavailable
To fix this, I attempted the following recommendation mentioned here, and modified the input like so:
npm uninstall -g submodule
npm cache clean
npm install -g submodule@latest
Taking this step provided output that looked promising, so I attempted the build, which failed because of the missing wil/Common.h

I'm looking to get past build, and based on other issues, it sounds like the git submodule update --init --recursive is my roadblock. Any help would be appreciated - thanks for your consideration.

Originally created by @phfbfc on GitHub (Jun 14, 2019). Followed README and build instructions from issue 489. Got stuck at: `git submodule update --init --recursive` Which yielded: `0 [main] sh 6324 fork: child 1504 - died waiting for dll loading, errno 11` `/mingw64/libexec/git-core/git-sh-setup: fork: retry: resource temporarily unavailable` To fix this, I attempted the following recommendation mentioned [here,](https://stackoverflow.com/questions/39803268/npm-install-error-receiving-fork-errors-died-waiting-for-dll-loading-errno-1) and modified the input like so: `npm uninstall -g submodule` `npm cache clean` `npm install -g submodule@latest` Taking this step provided output that looked promising, so I attempted the build, which failed because of the missing wil/Common.h I'm looking to get past build, and based on other issues, it sounds like the `git submodule update --init --recursive` is my roadblock. Any help would be appreciated - thanks for your consideration.
claunia added the Needs-Tag-FixResolution-Answered labels 2026-01-30 22:33:43 +00:00
claunia commented 2026-01-30 22:33:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 14, 2019):

This sounds like a git issue. Is it unique to the Terminal repo, or can you not init submodules for any git repo?

I'd look in #489, and follow up in the issue tracker for wherever you got git from.

@zadjii-msft commented on GitHub (Jun 14, 2019): This sounds like a `git` issue. Is it unique to the Terminal repo, or can you not init submodules for _any_ git repo? I'd look in #489, and follow up in the issue tracker for wherever you got `git` from.
claunia commented 2026-01-30 22:33:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 14, 2019):

Also, would you mind trying actual git for windows? It looks like this is mingw64's git, and I don't know how npm is getting involved here ...

@DHowett-MSFT commented on GitHub (Jun 14, 2019): Also, would you mind trying _actual git for windows_? It looks like this is mingw64's git, and I don't know how npm is getting involved here ...
claunia commented 2026-01-30 22:33:44 +00:00
Author
Owner
Copy Link

@burhan commented on GitHub (Jun 16, 2019):

Try using the github desktop, cloning the repository there and then following the steps.

@burhan commented on GitHub (Jun 16, 2019): Try using the [github desktop](https://help.github.com/en/desktop/getting-started-with-github-desktop/installing-github-desktop), cloning the repository there and then following the steps.
claunia commented 2026-01-30 22:33:44 +00:00
Author
Owner
Copy Link

@squeeter commented on GitHub (Jun 17, 2019):

Also, would you mind trying actual git for windows? It looks like this is mingw64's git, and I don't know how npm is getting involved here ...

@DHowett-MSFT: Good call on git for windows - I overlooked that this machine was running a different setup. As for npm, I was looking for solutions based on similar errors. At the time, I thought it was a git built-in.

@squeeter commented on GitHub (Jun 17, 2019): > Also, would you mind trying _actual git for windows_? It looks like this is mingw64's git, and I don't know how npm is getting involved here ... @DHowett-MSFT: Good call on git for windows - I overlooked that this machine was running a different setup. As for npm, I was looking for solutions based on similar errors. At the time, I thought it was a git built-in.
claunia commented 2026-01-30 22:33:45 +00:00
Author
Owner
Copy Link

@squeeter commented on GitHub (Jun 17, 2019):

Uninstalling/Reinstalling git solved this issue.

@squeeter commented on GitHub (Jun 17, 2019): Uninstalling/Reinstalling git solved this issue.
claunia commented 2026-01-30 22:33:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 18, 2019):

Thanks for testing.

@DHowett-MSFT commented on GitHub (Jun 18, 2019): Thanks for testing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1682
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?