Skip to main content

produced_http_response

Function produced_http_response 

Source
pub fn produced_http_response(results: &[ActionResult]) -> bool
Expand description

Did the model produce a usable send_http_response?

True when some Output payload parses as JSON — the same condition build_response uses to decide whether to answer from the model or fall back to the server’s default_response (or a blank 200).

It is public because the caller is where that outcome has to be logged: build_response is shared by every HTTP-shaped protocol and cannot know what any one of them wants to say about it. Callers use this rather than re-deriving the predicate, so the log line and the bytes on the wire cannot drift apart — a tag claiming the model answered while the peer received the fallback would be worse than no tag at all.