Re: Receiving console output from GIT 10mins after abort/termination?
From: "Frank Wolf" Sent: Wednesday, July 18, 2018 7:38 AM Hi @ll, I hope I'm posting to the right group (not sure if it's Windows related) but I've got a weird problem using GIT: By accident I've tried to push a repository (containing an already commited but not yet pushed submodule reference). This fails immediately with an error of course BUT after 10 mins I get an output on the console though the command exited!? (... $Received disconnect from : User session has timed out idling after 600 ms) Does anyone have an explanation why I still get an output after the command was aborted? /Frank I think this is a Windows environment issue. I have added a repy to the GitHub git-forwindows tracker. https://github.com/git-for-windows/git/issues/1762#issuecomment-406851107 I think you may have found a special case so will need extra details from you about the setup and hopefully an MVCE. Philip
Re: Receiving console output from GIT 10mins after abort/termination?
On Tue, Jul 17, 2018 at 11:38 PM Frank Wolf wrote: > > Hi @ll, > > I hope I'm posting to the right group (not sure if it's Windows related) but > I've got > a weird problem using GIT: > > By accident I've tried to push a repository (containing an already > commited but not yet pushed submodule reference). > This fails immediately with an error of course BUT > > after 10 mins I get an output on the console though the command exited!? > (... $Received disconnect from : User session has timed out > idling after 600 ms) This sounds like it is better suited for https://github.com/git-for-windows/git/issues/new as the error message suggests it comes from some software bundled with GfW to make Git work on Windows. (Gits source code doesn't contain such an error message)
Receiving console output from GIT 10mins after abort/termination?
Hi @ll, I hope I'm posting to the right group (not sure if it's Windows related) but I've got a weird problem using GIT: By accident I've tried to push a repository (containing an already commited but not yet pushed submodule reference). This fails immediately with an error of course BUT after 10 mins I get an output on the console though the command exited!? (... $Received disconnect from : User session has timed out idling after 600 ms) Does anyone have an explanation why I still get an output after the command was aborted? /Frank
