Skip to content

Commit 70e4524

Browse files
avitenzerclaude
authored andcommitted
docs(api): a zero or negative lava-relay-timeout is ignored (MAG-3988)
Magma-Devs/smart-router#452 stops a negative lava-relay-timeout from crashing the router by ignoring it, the same way an unparseable value already was. Say so next to the "used verbatim" promise, which still holds for every positive value. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
1 parent ceb92d6 commit 70e4524

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/api/directives.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ curl -X POST http://127.0.0.1:3360 \
7171
lava-relay-timeout: 12s
7272
```
7373

74-
Sets the timeout for each upstream attempt of this request. Format: any Go duration string (`500ms`, `5s`, `1m30s`). The value is used **verbatim** — unlike the server-side default it is *not* clamped to the `--min-relay-timeout` floor, so a client can ask for less.
74+
Sets the timeout for each upstream attempt of this request. Format: any Go duration string (`500ms`, `5s`, `1m30s`). The value is used **verbatim** — unlike the server-side default it is *not* clamped to the `--min-relay-timeout` floor, so a client can ask for less. A zero or negative value, like one that does not parse, is ignored: the request keeps the router's own timeout.
7575

7676
**When to use:** known-slow methods (`debug_traceTransaction` on a deep block), or known-fast methods you don't want to wait for.
7777

0 commit comments

Comments
 (0)