> It's pretty likely that you're being cut off by the idle timeout, but
> not at all clear why the connection was idle for an hour. That really
> shouldn't happen. You say this is repeatable?
The connection wasn't idle -- the progress line was updating steadily
right up to the hour mark, then stopped.
I tried it 3-4 times, IIRC, and all hung at an hour. Also (as I now
know from trying the suggested workaround of splitting the branch up
into an initial revision-limited branch followed by pulls with
progressively higher revision limits) that a pull time out if the
revisions it's inserting are big enough. That happened twice.
> Are you branching into a shared repo? I could just about imagine
> that a cross-format fetch might stall like this.
I didn't use a shared repo -- I only expect to need one web2py branch.
Michael, Tim --
> It's pretty likely that you're being cut off by the idle timeout, but
> not at all clear why the connection was idle for an hour. That really
> shouldn't happen. You say this is repeatable?
The connection wasn't idle -- the progress line was updating steadily
right up to the hour mark, then stopped.
I tried it 3-4 times, IIRC, and all hung at an hour. Also (as I now
know from trying the suggested workaround of splitting the branch up
into an initial revision-limited branch followed by pulls with
progressively higher revision limits) that a pull time out if the
revisions it's inserting are big enough. That happened twice.
> Are you branching into a shared repo? I could just about imagine
> that a cross-format fetch might stall like this.
I didn't use a shared repo -- I only expect to need one web2py branch.
-- Pat