pub enum LoopGuardTrip {
Loop,
Stagnation,
}Expand description
Which of the loop guard’s two detectors raised a trip.
The guard is two detectors behind one verdict, and until this existed their
trips went into one number, so nobody could ask whether stagnation trips
had become rare, which is the question that decides whether the proxy
keeps StagnationDetector in its guard (ADR 0011’s first kill criterion,
#947; retiring the detector itself also needs the agent path’s reading,
#1091).
Since #1052 a trip is an intervention rather than a rejection: the default
forwards the request with a note.
It says which detector, and nothing about which path. Only the proxy’s pre-dispatch scan records a trip at all: the agent loop runs the same two detectors and its trips reach no counter (#1091).
Variants§
Loop
The same tool-call batch repeated back to back and kept getting the same answer.
Also a batch that is not read-only carried past the read-only allowance by changing answers. The guard’s verdict does not tell those two apart, because the remedy is the same, so neither does this.
Stagnation
The same assistant text repeated beyond the threshold.
Trait Implementations§
Source§impl Clone for LoopGuardTrip
impl Clone for LoopGuardTrip
Source§fn clone(&self) -> LoopGuardTrip
fn clone(&self) -> LoopGuardTrip
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for LoopGuardTrip
impl Debug for LoopGuardTrip
Source§impl PartialEq for LoopGuardTrip
impl PartialEq for LoopGuardTrip
Source§fn eq(&self, other: &LoopGuardTrip) -> bool
fn eq(&self, other: &LoopGuardTrip) -> bool
self and other values to be equal, and is used by ==.