Closed
Bug 1659842
Opened 5 years ago
Closed 5 years ago
Can't use normandy.liveTelemetry in filter expressions
Categories
(Firefox :: Normandy Client, defect)
Firefox
Normandy Client
Tracking
()
RESOLVED
FIXED
81 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox-esr78 | --- | unaffected |
| firefox79 | --- | unaffected |
| firefox80 | --- | wontfix |
| firefox81 | --- | fixed |
People
(Reporter: mythmon, Assigned: mythmon)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The targeting changing made in bug 1644743 force a direct evaluation of context items used, and don't catch any errors that might result. For simplicity it awaits all values, which in the case of normandy.liveTelemetry causes it to be treated as a promise (which it is not). The live telemetry value asserts that the only valid way to use it is as normandy.liveTelemetry.main to provide nicer errors. .then is not .main, and so it throws an error that isn't important.
The live telemetry accessor shouldn't error out when it's .then attribute is accessed.
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Comment 2•5 years ago
|
||
Set release status flags based on info from the regressing bug 1644743
status-firefox79:
--- → unaffected
status-firefox80:
--- → affected
status-firefox81:
--- → affected
status-firefox-esr68:
--- → unaffected
status-firefox-esr78:
--- → unaffected
Pushed by mcooper@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/78ee24737069
Make normandy.liveTelemetry accessible from consolidated targeting r=andreio
|
||
Updated•5 years ago
|
Flags: in-testsuite+
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
|
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•