Re: [Monotone-devel] Fatal error: std::runtime_error

[Jens Seidel]

On Mon, Apr 09, 2007 at 12:20:49PM +0200, Markus Schiltknecht wrote:
> Jens Seidel wrote:
> >mtn: Fatal error: std::runtime_error: network error: recv failure:
> >Timeout for the connection expired
> 
> Hm.. doesn't look like a bug in monotone, does it?

Maybe it's an option to increase the timeout? I have an ordinary DSL
connection and the router may disconnent after some time of inactivity.
This does not affect other programs negatively!

> >As usual monotone did not stopped after recieving the last revision
> >(165). There was no CPU usage and the memory usage was constant (40%).
> >Normally I kill it using Ctrl+C but this time I waited longer and got
> >the error. I waited at least 30 minutes ...
> 
> Hm.. so your real complaint is, that monotone doesn't properly err out 
> on disconnect?

I just cannot assume that it's the normal bahaviour to kill monotone
after fetching the last revision. I don't know what tasks are performed
by monotone after it but it's no option to wait a really long time for
the error mentioned above.

Please note that I use a slow computer PIII 800MHz and I remember that
the first checkout of openembedded required more than a day ...

I tried
 $ mtn --db=oe.db pull monotone.openembedded.org org.openembedded.dreambox
again and this time it stopped properly and immediately after the last
revision was fetched.

> Any idea on what's happening on the server side?

I? Sorry, I don't now anything about openembedded or monotone. I'm a
subversion/CVS user most of the time :-(

Jens