Closed Bug 411680 Opened 14 years ago Closed 13 years ago

Always show more details about update check failures in the error console

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.3a1
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: mossop, Assigned: mossop)

Details

Attachments

(1 file)

Shaver suggests that when an addon update check fails and we just show "there was an error checking for updates" in hte UI that we should always include the error in the console for users to see and pass on to developers.

Don't really think this is blocking but if it's a wanted I may be able to find the time for it.
Flags: blocking-firefox3?
This does not block the final release of Firefox 3.
Flags: wanted-firefox3+
Flags: blocking-firefox3?
Flags: blocking-firefox3-
Product: Firefox → Toolkit
Target Milestone: --- → mozilla1.9.1
Target Milestone: mozilla1.9.1 → mozilla1.9.2
Attached patch patch rev 1Splinter Review
This gives us three different logging functions, LOG, WARN and ERROR. LOG does nothing if the preference extensions.logging.enabled is false. When the pref is true it logs to the error console and the text console. WARN and ERROR both always log to the error console and when the pref is true will also log to the text console. ERROR additionally always logs to the log file in the profile folder.

The intention is that LOG is for tracing messages useful for debugging the add-ons manager itself. WARN is for messages that add-on developers will find useful in tracking down problems with installation and updates. ERROR is for problems that are likely in the add-ons manager itself and need to be logged so that we can track them down.

For this bug I've just made the cases where updates fail a warning.
Assignee: nobody → dtownsend
Status: NEW → ASSIGNED
Attachment #395031 - Flags: review?(robert.bugzilla)
Comment on attachment 395031 [details] [diff] [review]
patch rev 1

Looks fine. There is a lot of inconsistency with the string format passed to these functions. I've seen
1. strings that end with \n while others don't.
2. long strings that contain \r\n, other long strings that contain \n, and other long strings that don't have any type of newline.

Might be a good thing to file a followup to clean this up.
Attachment #395031 - Flags: review?(robert.bugzilla) → review+
Comment on attachment 395031 [details] [diff] [review]
patch rev 1

Another thing that I think would be nice is to denote where these logs are coming from along the lines of EM_LOG, EM_WARN, and EM_ERROR or something similar.
Landed: http://hg.mozilla.org/mozilla-central/rev/325a834b759c
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [needs baking]
Target Milestone: mozilla1.9.2 → mozilla1.9.3a1
Comment on attachment 395031 [details] [diff] [review]
patch rev 1

This change only affects the error console and provides an easier way for extension developers to debug issues with extension update. This is a low risk change and has been baking on trunk.
Attachment #395031 - Flags: approval1.9.2?
Whiteboard: [needs baking]
Comment on attachment 395031 [details] [diff] [review]
patch rev 1

a192=beltzner
Attachment #395031 - Flags: approval1.9.2? → approval1.9.2+
You need to log in before you can comment on or make changes to this bug.