c2c-oerpscenario team mailing list archive

[OpenERP buildbot <682801@xxxxxxxxxxxxxxxxxx>]

On Monday 29 November 2010, you wrote:
> Public bug reported:
> 
> Steps to reproduce:
> 0. Put server or client in debug_rpc mode for easier diagnostics
> 1. Login onto a working OpenERP Server with GTK client, until you see the
> menu 2. Stop the server, then start it again with an invalid database
> username or password (e.g. -r foobar) 3. In GTK, try to refresh the menu
> that is still open (CTRL-R)
> 4. See that the GTK client loops endlessly, trying to call
> maintenance.contract.status(), until you stop the server
> 
> -> Errors should be caught when calling maintenance.contract.status()
> with a fallback that shows the error even if the maintenance status
> could not be determined.
> 
> See also:  bin/common/common.py:397 (from revision 1703)

Long fixed in Gtk client, see trunk-xrg branch.


-- 
Say NO to spam and viruses. Stop using Microsoft Windows!

-- 
Loop looking for maintenance contract when server is broken
https://bugs.launchpad.net/bugs/682801
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject GTK Client: Confirmed

Bug description:
Steps to reproduce:
0. Put server or client in debug_rpc mode for easier diagnostics
1. Login onto a working OpenERP Server with GTK client, until you see the menu
2. Stop the server, then start it again with an invalid database username or password (e.g. -r foobar)
3. In GTK, try to refresh the menu that is still open (CTRL-R)
4. See that the GTK client loops endlessly, trying to call maintenance.contract.status(), until you stop the server

-> Errors should be caught when calling maintenance.contract.status() with a fallback that shows the error even if the maintenance status could not be determined.

See also:  bin/common/common.py:397 (from revision 1703)

Thanks!