tassert instead of invariant if checking feature flags on undefined FCV

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: 7.0.0, 8.0.0, 8.3.0-rc0, 8.2.0
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-02-02
    • 1
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Currently checking a FCV-gated feature flag under undefined FCV using FCVGatedFeatureFlag::isEnabled causes the Server to crash (invariant).

      We could make this a tripwire assert instead of an invariant, since generally it's safe to abort the operation.

      (The way the invariant happens is that FCVGatedFeatureFlag::isEnabled calls FCVSnapshot::getVersion, which contains the invariant.)

            Assignee:
            Marco Bizzarri
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: