product · inferred from evidence
Flipt
A feature flag management tool mentioned as having a regression in versions 1.9.0 and 1.10.0.
- Flipt 1.5.0 evaluate API invalid value for string type null on null context values
POSTing to /api/v1/evaluate with a null context value, e.g. {"flag_key":"profile","entity_id":"...","context":{"cohort":null}}, returns HTTP 400 with {"code":3,"message":"proto: (line 1:102): invalid value for string type: null"}. This was
- Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy
Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked f
- ChromaDB DuplicateIDError on memgpt load (duplicate embedding IDs)
Running `memgpt load` with a large .jsonl dataset failed with "chromadb.errors.DuplicateIDError: Expected IDs to be unique, found duplicates of: ...". The dataset produced duplicate embedding IDs on load, and Chroma's `validate_ids` rejecte
- Flipt v2 high memory consumption 800MB with git storage in Kubernetes
Flipt v2.0.1 in Kubernetes consumes 550-800 MB of memory with only 4 flags, configured with 4 environments backed by 2 git storage projects. The git repositories are GitOps repos for ArgoCD with substantial history, and Flipt appeared to ho
- Flipt ERROR invalid input syntax for type integer OR_SEGMENT_OPERATOR SQLSTATE 22P02
Running Flipt with Helm and an on-premise Postgres database, everything works until you try to modify any entity: editing a variant flag or a segment constraint fails with ERROR: invalid input syntax for type integer: "OR_SEGMENT_OPERATOR"
- Flipt export fails on variant flag with no rules wrong format for rule segments
Exporting Flipt state fails with "wrong format for rule segments" when a variant flag has no rules attached yet. Steps: create a variant flag, do not add rules, run export. The export should succeed even for rule-less flags, since that is a