433925 - Better error reporting and handling

Status: RESOLVED FIXED

(Cloud Services :: General, defect, P1)

Description

[Dan Mills [:thunder]]

Currently errors will cause the status bar to say 'error'.  For more details, the only place to go is the sync log, either the brief or verbose, and try to glean the cause of the error from that.

This could be greatly improved.  Is it a network condition?  Data corruption?  A client-side problem?  Is it transient or permanent?  And perhaps most importantly, what are the suggested steps for fixing the problem?

Comment 1

[Dan Mills [:thunder]]

Punting to 0.3.

Comment 2

[Vasili Gulevich]

Log is a very nice thing. The combination of logged information doesn't seem to be complete, though. (I can't say what I want to see there also.)
Removing log is a crime :)

By the way, status bar popup is buggy. The yellow warning icon in status bar won't disappear even if all messages are cancelled by hand.

This might be the right place to report, that all info (blue icon) messages in popup have no text for me (empty messages?). I'm using English and Russian localization of Firefox and that is true for both of them.

Comment 3

[Dan Mills [:thunder]]

(In reply to comment #2)

> By the way, status bar popup is buggy. The yellow warning icon in status bar
> won't disappear even if all messages are cancelled by hand.

This should be filed as a separate bug, as it's not related to this one.

> This might be the right place to report, that all info (blue icon) messages in
> popup have no text for me (empty messages?). I'm using English and Russian
> localization of Firefox and that is true for both of them.

This should also be a new bug.  I haven't seen this before.

Comment 4

[Gaspard Leon]

A good example of this bug is today I opened firefox and I have the yellow error triangle and I'm not logged in.

So I click it:
Error While Signing In
Weave encountered an error while signing you in. Your username/password failed. Please try again.

Further investigation of the logs revealed:
------------------------------------------------------------------
2008-07-24 09:52:08	Service.Util	ERROR	Login verification failed Error code: 503
2008-07-24 09:52:08	Service.Main	INFO	Making sure server is initialized...
2008-07-24 09:52:08	Service.Util	ERROR	Cannot initialize server Error code: 503
------------------------------------------------------------------

Code 503 looked like a service unavailable error to me so I went to:
https://services.mozilla.com/user/gaspard.leon/
------------------------------------------------------------------
Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.3 (Red Hat) Server at services.mozilla.com Port 443
------------------------------------------------------------------

So I found the source of the problem, the server is down for maintenance or overloaded...

It would be nice if weave could pass this error through to the sign in or if the server status code is in the 500 range, maybe it could say:
"The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."

Without this, I'm left wondering if someone hacked my account and changed my password, or if I typed it wrong, or what...

Comment 5

[Dan Mills [:thunder]]

These bugs need to be triaged, removing 0.3 milestone setting.

Comment 6

[Dan Mills [:thunder]]

This bug was well-intentioned, but too vague to be useful.  We've improved error handling and reporting since this bug was originally filed, so I will close it as fixed.  Please file separate bugs for specific problems if/when they are found.