Closed Bug 572855 Opened 14 years ago Closed 14 years ago

FlightDeck addon doesn't log in-development addon's console messages to forsaken console

Categories

(Mozilla Labs Graveyard :: FlightDeck, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: avarma, Assigned: avarma)

Details

Thanks to bug 570856, in the forsaken console one can see all of the FlightDeck addon's debugging messages about what files it's unzipping and other details irrelevant to FlightDeck users, but they can't actually see the console messages their own addon logs--those are still being sent to stdout.

This shouldn't be too difficult to fix, but it's basically a blocker for FlightDeck IMO.
Assignee: nobody → avarma
Severity: normal → blocker
Priority: -- → P1
Also, the irrelevant logging messages from the FD addon itself should be removed, as the spam about files being unzipped will make development a lot harder for FD users.
This required two separate pushes to two separate repositories to fix:

  http://hg.mozilla.org/labs/jetpack-sdk/rev/bbb1288e86e0

  http://github.com/toolness/addons-builder-helper/commit/8c6b7976896cf33c34e9348c75cfbe495f989464

It's done now, though piotr will need to re-spin the XPI on the development server so it gives users the latest version. I'm not sure if his XPI has an update.rdf associated with it--if not, users will need to manually install the new version. (We should also make sure we have an update.rdf for the real FD addon once we go live.)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Shouldn't we be distributing the helper addon from AMO?
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.