Closed
Bug 1816463
Opened 2 years ago
Closed 2 years ago
The CBH Nimbus feature configuration does not accept integers from the implemented range
Categories
(Core :: Privacy: Anti-Tracking, defect, P2)
Tracking
()
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox110 | --- | unaffected |
firefox111 | --- | affected |
firefox112 | --- | unaffected |
People
(Reporter: ppop, Assigned: jlockhart)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-cookie-banner-v1])
Attachments
(3 files)
[Prerequisites]:
- Have access to the Nimbus Experimenter page(LDAP).
[Steps to reproduce]:
- Open the browser with the profile from prerequisites.
- Navigate to the Branches page of a Nimbus Experiment using the CBH feature. (https://stage.experimenter.nonprod.dataops.mozgcp.net/nimbus/ppop-cbh-handling-test/edit/branches)
- Observe the "Value" field of the branches.
[Expected result]:
- The JSON is validated and no errors are displayed.
[Actual result]:
- The "1 is not one of ['0', '1', '2']" error is displayed and the JSON is invalid.
[Notes]:
- Attached a screenshot of the issue on the Experimenter page, as well as screenshots of the feature configs of both Searchfox and the Nimbus Admin:
Reporter | ||
Comment 1•2 years ago
|
||
Reporter | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
QA Whiteboard: [fidefe-cookie-banner-v1]
Updated•2 years ago
|
QA Whiteboard: [fidefe-cookie-banner-v1]
Whiteboard: [fidefe-cookie-banner-v1]
Updated•2 years ago
|
Updated•2 years ago
|
Assignee: nobody → jhirsch
Priority: -- → P2
Comment 3•2 years ago
|
||
it looks like enums don't support integers, so the right fix here is probably to have string names for the variants. planning to fix this along with the fix for bug 1816464.
Assignee | ||
Comment 4•2 years ago
•
|
||
This is a bug in Experimenter, filed here:
Comment 5•2 years ago
|
||
OK, and looks like this was already fixed. Thanks :jlockhart! I can't dupe this to a github bug, so I'll assign it to you and mark it as fixed.
Assignee: jhirsch → jkerim
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Comment 6•1 year ago
|
||
Marking this as verified as the feature configuration is no longer available and the issue is no longer reproducible due to this.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•