BackendOutcome#
- class scikitplot.corpus.BackendOutcome(status, value, backend, attempted, missed, errors, skipped=(), policy='resilient', selected_capabilities=(), active_capability=None, skip_details=(), requested_backend=None, allow_fallback=True)[source]#
Structured, serialisable outcome from
run_backend_chain.Notes
User. The fallback vocabulary (R2-5) shared with the vector backends and
SemanticChunker:requested_backendis the first candidate the policy allows to run (a candidate the policy skips – network disabled, not ready – was never eligible, like an absent backend under"auto";skippedandskip_detailsrecord it),backendthe one that produced the value,allow_fallbackthe policy’s switch (False: no other candidate is attempted), andfallback_reasonwhy they differ:"failed"(it raised) or"no_result"(it returned nothing usable).- Parameters:
status (BackendStatus)
value (_T)
backend (str | None)
errors (tuple[ErrorRecord, ...])
policy (str)
active_capability (str | None)
skip_details (tuple[BackendSkip, ...])
requested_backend (str | None)
allow_fallback (bool)
- capability_view(*, registry=None)[source]#
Return readiness records with selected/active runtime provenance.
- errors: tuple[ErrorRecord, ...][source]#
- property fallback_reason: str | None#
Why
backendis notrequested_backend, orNone.- Returns:
- str or None
"failed"or"no_result"for the requested candidate’s fate;Nonewhen it produced the value, or when no candidate was eligible.
- skip_details: tuple[BackendSkip, ...] = ()#
- status: BackendStatus[source]#