Add some safeguards around the Nimbus C++ API
Categories
(Firefox :: Nimbus Desktop Client, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox156 | --- | fixed |
People
(Reporter: beth, Assigned: beth, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [nimbus])
Attachments
(1 file)
We just had a case where a feature was misconfigured and could not use the C++ feature API because isEarlyStartup was false. This made it all the way to release without getting caught.
Instead, we should have some klaxons go off if you call into the feature API for an unsupported feature, e.g., a MOZ_DIAGNOSTIC_ASSERT.
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
Comment 4•2 months ago
|
||
Backed out for causing failures regarding Nimbus , FeatureManifest.yaml
| Assignee | ||
Updated•2 months ago
|
Comment 5•2 months ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 1 week.
:beth, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 months ago
|
Backed out for causing gtest failures related to gtest.NimbusTelemetryFixture
Backout link
Push with failures
Failure log(s)
| Assignee | ||
Updated•17 days ago
|
| Assignee | ||
Updated•15 days ago
|
Comment 10•13 days ago
|
||
| bugherder | ||
Updated•7 days ago
|
Description
•