Time out

[Todd O'Bryan]

I'm using Mercurial Eclipse in a high school class that I teach. We
use a thin-client Linux lab, so it's not uncommon for 12 or 13
students to be using the same server to do their work. Unfortunately,
especially when we try to merge, we get lots of timeout errors,
probably because the server is busy processing other requests. Using
"hg merge" from the command line works, but we lose the very nice
Merge view that Mercurial Eclipse provides.

Any idea how to avoid the timeout issues?

Todd

[Zingo Andersen]

Hi
Nice to hear that you have some use for Mercurial Eclipse!

There are some timeout values you can play with in the preference page under
Team -> Mercurial Eclipse -> Timeouts

You can also add some extra output in the Mercurial Console in the prefs if you do
you can check it on how long it took to execute the commands if you
open the mercurial console (check in the console view there should
be some way to select it)

If you manage to figure out a better value please let us know so we can
update the default value and make a release for you so you don't need
to reconfigure all clients.

Hope this helps you!

--
Zingo "Stefan" Andersen (zingo.org and vectrace.com)

[Marcus Lindblom]

I thought merge was a local operation, i.e. disconnected from server? Or
does ME access the server anyway?

Cheers,
/Marcus

[Marcus Lindblom]

I thought merge was a local operation, i.e. disconnected from server? Or

[Bastian Doetsch]

No, it doesn't it is local. But maybe they use Samba which slows down
Mercurial quite a bit...

>
> Cheers,
> /Marcus

[Todd O'Bryan]

Sorry for the confusion. When I say "server", I mean the application
server that all the thin clients run on, not the Mercurial server
where the remote repos are saved. I upped the timeout to 360000 and it
seemed to work.