\Drupal\strata\Health\Tripwire KeyRotatedMidFlight

One segment's frames need more than one key to open.

The symptom of a rotation that landed while a flush was in progress: some frames in the window were sealed with the outgoing key and the rest with the incoming one. Both open, so nothing is lost, and that is exactly why it needs saying - the store is readable now and stops being readable the moment the retired key is removed from the ring.

A whole segment sealed under one retired key is NOT this symptom. That is a segment that predates the rotation, which is the normal state of every byte written before it and is what the ring exists to handle. The finding is about a segment split ACROSS keys.

Summary

Methods
Properties
Constants
code
check
No public properties found
No public constants found
No protected methods found
No protected properties found
No protected constants found
No private methods found
No private properties found
No private constants found

Methods

code()

code() : string

The stable dotted code every finding from this tripwire reports under.

Returns

string —

For example "frame.digest_mismatch".

check()

check(array  $observation) : \Drupal\strata\Health\Finding|null

Evaluates the check against one observation.

Parameters

array $observation

Expects segment and fingerprints, the distinct key fingerprints that opened its frames.

Returns

\Drupal\strata\Health\Finding|null —

A finding when the symptom is present, or NULL when the check is satisfied.