Guardrail services merged the stricter way; the request log keeps no restored value
CI / test (push) Failing after 7m44s
CI / test (push) Failing after 7m44s
From review. - A service two policies name is asked the stricter way of the two, both directions and block over flag, rather than as the first one says. - A service answering null where it says unsafe gave no answer, not safe. - With restore: true, the kept answer had the request's redacted values in it beside the redacted request; they are taken out again before it is kept. - guardrails.md says what fail: open lets through, and that of n answers a service reads the first. - The similar cache's embedding failures are logged once a minute, not per request; the page's test reads the gateway's local MCP handler under its lock; org/name:Q4_K_M is not taken for a Hugging Face id to read as safetensors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
f94d902cc3
commit
5eac62d556
10 files changed
+74
-8
No files matched your search
+4
-1
@@ -309,7 +309,10 @@ service can stop a streamed answer only where it is held back
|
||||
it by then, and what the service finds ends the stream with
|
||||
`content_filter`, flags it and is recorded. The rule recorded is
|
||||
`service:<name>:<reason>`. The service is told the text only, never who
|
||||
sent it.
|
||||
sent it. Under `fail: open`, the default, a service that cannot be asked
|
||||
lets the text through — and a caller can make it fail, sending what it
|
||||
refuses to read; give `fail: closed` where the service must decide. Of an
|
||||
answer asked for with `n` above 1, the service reads the first.
|
||||
|
||||
## Where a policy applies
|
||||
|
||||
|
||||
Reference in new issue
Block a user