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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Breaking Changes
Streams are on by default (#1275).streamStore.backend now defaults to memory for serve as well as dev. A config without a streamStore section keeps Stream messages in the active process's memory instead of rejecting client Stream calls. Set streamStore.backend: disabled for the previous behavior; client Stream calls then fail with FAILED_PRECONDITION.
Stream memory bounds. New streamStore.maxTotalBytes (default 1 GiB) caps Stream data on a node; a write past it returns RESOURCE_EXHAUSTED, and background trimming removes the oldest messages of the largest Streams. A stream_capacity_bytes above streamStore.maxStreamCapacityBytes (default 64 MiB) is clamped.
Capacity rejection text. A message whose charge exceeds its Stream's capacity still returns RESOURCE_EXHAUSTED, now with "Stream message charge exceeds the Stream capacity, so it can never fit", and no longer trims that Stream.
server-zd v0.1.19
Features
New metric dexzd_step_stream_writes_dropped_total{reason} counts Step Stream writes that were dropped (disabled, invalid_argument, message_too_large, stream_capacity_exceeded, total_capacity_exceeded, closed). Step Stream writes stay best effort and never fail the Step.
A startup warning when streamStore.backend is disabled.
Fixes
streamStore.estimatedMessageOverheadBytes, backgroundTrimBatchSize, trimBatchYieldTime, and trimWorkers were validated but ignored. They now take effect, with unchanged defaults.
A rejected Stream write asks trimming to free room for itself, so writes cannot stay rejected while usage sits at the trim target.
Message identities stay increasing when trimming removes a Stream and a write recreates it, so a resume token never skips a new message.
Upgrade
Stop every old process, including standbys, then start v0.1.19.
Before server-zd 1.0, rolling a node back to an older 0.x binary after a newer one has run is not supported.
Artifacts
Container image dex-server-zd:0.1.19 for linux/arm64 and linux/amd64.
dex-server-zd binaries for Linux amd64, Linux arm64 (glibc 2.28 or newer), macOS arm64 and macOS amd64, with checksums.txt.