Closed Bug 1474397 Opened 6 years ago Closed 4 years ago

Show Normandy information in about:support

Categories

(Firefox :: Normandy Client, enhancement, P3)

Product:
Firefox
Component:
Normandy Client
Type:
enhancement

Tracking

()

Status:
VERIFIED FIXED
Milestone:
87 Branch
Tracking Flags:
Tracking Status
firefox87 --- verified

People

(Reporter: mythmon, Assigned: mythmon)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Bug 1474397 - Show Normandy information in about:support r=gijs
(deleted), text/x-phabricator-request
Details
Bug 1474397 - Only try to import normandy modules in about:support / Troubleshoot.jsm, if normandy is enabled. r=gijs
(deleted), text/x-phabricator-request
Details
Bug 1474397 - followup to really not try to import normandy modules in about:support / Troubleshoot.jsm, if normandy is enabled. r=Gijs
(deleted), text/x-phabricator-request
Details
The list of currently active preference studies should be shown in about:support. It should not include expired studies.
Is there a reason for which we don't want to show expired pref-studies? It would seem reasonable to me to be transparent on the expired pref-studies as well, since we do the same with add-on studies.
about:support is about the current things affecting the browser, not a historical record of what has happened. about:studies will eventually show the historic record, in bug 1447499. This isn't about being transparent about studies, but about having an easy place to send users to see if they are affected by a pref flip.
Priority: -- → P3
Blocks: 1574577
Summary: Show preference studies in about:support → Show Normandy information in about:support
Assignee: nobody → mcooper
Status: NEW → ASSIGNED
Pushed by mcooper@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ba66119d9f52 Show Normandy information in about:support r=Gijs

https://hg.mozilla.org/mozilla-central/rev/ba66119d9f52

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox87: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch

This is breaking some Thunderbird tests (since no normandy).

Attachment #9203910 - Attachment description: Bug 1474397 - Only try to import normandy modules if normandy is enabled. r=gijs → Bug 1474397 - Only try to import normandy modules in about:support / Troubleshoot.jsm, if normandy is enabled. r=gijs
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/1fcf4b2782e1 Only try to import normandy modules in about:support / Troubleshoot.jsm, if normandy is enabled. r=Gijs

Sorry I had misread the code a bit. Will need a followup to add an early return.

Oops, thanks for the follow ups Magnus. I didn't realize that lazy imports would still cause problems even if they weren't used.

Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/11fdc4a5ac73 followup to really not try to import normandy modules in about:support / Troubleshoot.jsm, if normandy is enabled. r=Gijs

I've verified that Preference Rollouts, Multi-preference Experiments, and Addon experiments are displayed in the about:support page on the latest Firefox Nightly 87.0a1 (Build ID 20210222084406) using Windows 10, macOS 11.2.1, Linux MX 4.19:

  • Preference rollouts in the Remote Features section
  • Multi-preference Experiments and Addon Experiments in the Remote Experiments section

@mythmon, were Addon rollouts left out intentionally? And should I reach out to the UJET team to have Nimbus experiments show up in the about:support page as well?

Flags: needinfo?(mcooper)

(In reply to Ciprian Muresan [:cmuresan], Ecosystem QA from comment #17)

@mythmon, were Addon rollouts left out intentionally? And should I reach out to the UJET team to have Nimbus experiments show up in the about:support page as well?

Yes, and yes. Addon rollouts never reached a level of completeness that we were happy using. We don't consider it to be a production quality service offered by Normandy at this time. Since Nimbus experiments have a different structure than Normandy, that will be a different implementation bug, and I think the UJET team would be best suited for it.

Flags: needinfo?(mcooper)

Great! Thanks for the answers. I'll mark this as Verified based on comment 17 and comment 18.

Status: RESOLVED → VERIFIED
status-firefox87: fixed → verified
Regressions: 1695451
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: