> they've been pretty silent on the bug that someone else filed about this
Hi ori_b, do you have a link to an issue for this? Happy to bring this up to the team for prioritization.
Hi ori_b, do you have a link to an issue for this? Happy to bring this up to the team for prioritization.
Apparently it can deadlock processes on the server, stopping the clone -- and they never get cleaned up. While they don't prevent anyone else from using the machine, they do sit around wasting resources, and potentially causing a denial of service attack.
I figured out bugs for github's issues, but I haven't been able to find one for gitlab's, and they've been pretty silent on the bug that someone else filed about this as far as I can tell.
It didn't feel like a particularly easy to trace system when I tried debugging.