Faultline

Memory tools

TimelinecheckoutReplay / DiffdiffBlameblameBisectbisectImpactimpactHandoffhandoffBenchtest

Tenant

tenant-synthetic

Synthetic Project Atlas data. One FalkorDB graph per tenant.

maannaan/faultline
faultline/bisect
Checking graph
TimelineReplay / DiffBlameBisectImpactHandoffBench

faultline bisect

Memory bisect

The answer was right at one time and different later. Bisect binary-searches the recorded memory between them and names the event and source that flipped it. Every probe is an as-of query against FalkorDB; nothing is written.

Range

Like git bisect, it assumes the answer flips once in the range.

Run bisect with the defaults: deploy_region was region-a on 15 Oct and region-b on 16 Oct. Which recorded event changed it?