1881409 - Old global config seems to persist even after ingesting an empty config

Status: NEW

(Application Services :: Suggest, defect, P3)

Description

[Drew Willcoxon :adw]

I'm hitting a test failure in bug 1881073 that seems to indicate a previous non-empty global config persists even after ingesting a new global config that's simply an empty object, {}. The failure only happens when running multiple browser tests. The test that fails sets the global config to an empty object, but show_less_frequently_cap in the config seems to retain its old value, presumably from a previous test. I haven't investigated it much. An easy way to verify this would be to add a Rust test function to store.rs.