Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

docs(evals): name --on-error in the sentence that already describes skipping

Aashish10f9c702f6d7
diff --git a/docs/evals.md b/docs/evals.md
index 0e11aefc..3ebe91b9 100644
--- a/docs/evals.md
+++ b/docs/evals.md
@@ -113,10 +113,11 @@ requests were served fast, not whether the run was cheap. With no `--batch-size`
timing noise. What the harness actually did -- the batch size asked for, the runner shape it
resolved to, how many rows shared a call, and the largest chunk -- is recorded in the report's
`config.timing`, because the flag alone does not say whether anything was batched. Those counters
-record the calls issued, not the calls that returned: with `on_error=skip`, a chunk whose call
-raised still counts in `rows_grouped` and `max_chunk`, next to its entries in `config.errored`. The
-two `*_ms` metrics count only the calls that returned, so a failed call never contributes a latency
-it did not measure.
+record the calls issued, not the calls that returned: with `laya-evals run --on-error skip`, a
+chunk whose call raised still counts in `rows_grouped` and `max_chunk`, next to its entries in
+`config.errored`. The default is `--on-error fail`, which re-raises instead of publishing a report
+whose metrics cover only the calls that came back. The two `*_ms` metrics count only the calls that
+returned, so a failed call never contributes a latency it did not measure.
### Grouping the rows inside a batch