[TriLUG] git push issue ( 20th )

Brian McCullough via TriLUG trilug at trilug.org
Tue Feb 21 10:43:27 EST 2023


On Mon, Feb 20, 2023 at 07:32:53PM -0500, Christopher Johnson wrote:
> Just kind of spitballing based on having used git a lot in my job but based
> on this documentation

Thank you, Christopher.


Further experimentation tells me that moving the "pre-push" hook
contents to "pre-commit" seems to cure the timeout problem, since there
is no apparent communication with BitBucket during that step.


> Depending on the method for connecting (ssh, git, or http(s)), I'm
> wondering if the test run is taking too long and the connection timeouts
> with no data being sent in that amount of time. Depending on the protocol,
> you might be able to configure it to keep the connection alive.

That was my suspicion, too.  However, I have no control over the
duration of the timeout at the BitBucket end, and that seems to be where
the problem is.


> Hope that helps,
> CJ


Thank you for the suggestions which confirmed my experimental results.


Now, let's see if the rest of the group agrees.


B



More information about the TriLUG mailing list