Open koistya opened 4 years ago
Sometimes I really think it's hanging because when I hit CTRL-C
and try to go to the cloned folder it works just fine, and sometimes it does not hang.
This happens on an Arch Linux installation using NPM 8.19.2
and Node 19.3.0
and really not sure what happens when it hangs because there is no output.
Confirming it works correctly and within seconds, but the console process takes a minute or so for some reason.
just happened to me
Happening to me too with degit@2.8.4
.
'c.
,xNMM. -----------------------------------
.OMMMMo OS: macOS 14.3 23D56 arm64
OMMM0, Host: Mac15,7
.;loddo:' loolloddol;. Kernel: 23.3.0
cKMMMMMMMMMMNWMMMMMMMMMM0: Uptime: 2 days, 22 hours, 40 mins
.KMMMMMMMMMMMMMMMMMMMMMMMWd. Packages: 69 (brew)
XMMMMMMMMMMMMMMMMMMMMMMMX. Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM: Resolution: 1920x1080, 1920x1080
:MMMMMMMMMMMMMMMMMMMMMMMM: DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX. WM: Rectangle
kMMMMMMMMMMMMMMMMMMMMMMMMWd. Terminal: iTerm2
.XMMMMMMMMMMMMMMMMMMMMMMMMMMk Terminal Font: JetBrainsMonoNFM-Regular 12
.XMMMMMMMMMMMMMMMMMMMMMMMMK. CPU: Apple M3 Pro
kMMMMMMMMMMMMMMMMMMMMMMd GPU: Apple M3 Pro
;KMMMMMMMWXXWMMMMMMMk. Memory: 3517MiB / 18432MiB
.cooc,. .,coo:.
It clones the repos as expected, but it just takes awhile to get the shell handed back after the cloned <repo> to <dest>
message gets logged.
Maybe the wording should be changed to cloning
instead of cloned
to indicate there's still some processing going on?
Otherwise, it's not clear if it's actually cloning the repo or hangs.