You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f09a512
Browse filesBrowse the repository at this point in the historyBrowse files
- ConstraintEnforcer: named-only specs (position -1) are looked up by name
and no longer consume a positional slot, so a named arg is checked against
its own value and the positional consts after it read the right slot.
Varargs consts check every value.
- pattern is an unanchored search (Matcher.find), matching JSON Schema/ECMA
and the Rust and Go SDKs; anchor with ^/$ for a full match.
- HTTP: when no tokenKey is configured, the stream-state token key is derived
from the signing key (HKDF-SHA256, label vgi.http.state_token_key.v1), so
table-function streams resume across replicas and restarts. Without a
signing key the per-process key stays and a warning is logged.
- Catalog listing: an onBind that throws on the empty-argument probe no
longer breaks ATTACH; the function is advertised with an empty output
schema and validated at the real bind.
Bump to 0.46.1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The `launch:` location scheme starts the worker once behind a flock-coordinated Unix socket and reuses it across queries and engine processes — essential for JVM workers, which are expensive to cold-start. Plain subprocess (`/path/to/worker`) and `http(s)://` locations also work.
145
145
146
+
## Running several HTTP replicas
147
+
148
+
Set the same `VGI_SIGNING_KEY` (or call `Worker.signingKey(byte[])`) on every
149
+
replica. It seals `attach_opaque_data` and, through an HKDF-SHA256 derivation
150
+
(label `vgi.http.state_token_key.v1`, never the raw key), keys the HTTP
151
+
stream-state tokens, so a table-function stream started on one replica resumes
152
+
on any other and survives a restart. Without it each process uses a random key
153
+
and logs a warning at startup. An explicit `HttpServer.Config.Builder.tokenKey`
154
+
still takes precedence.
155
+
146
156
## Example worker
147
157
148
158
For authenticated `iroh://` and HTTP-semantics `httpi://` deployments, see
0 commit comments