Repository navigation
Pixels 3.1.1
Hotfix on top of 3.1.0. WADO-RS metadata requests for very large series no longer time out or stall the gateway.
Fixes
- Large series metadata (#256): ingestion stores binary DICOM elements inline as base64, so series with large vendor private elements could carry hundreds of MB of metadata. The gateway took minutes to fetch and parse it, and other requests waited.
- Series and study metadata queries now drop any binary or private element larger than
PIXELS_METADATA_INLINE_BINARY_MAXcharacters (default4096) on the warehouse. - The gateway also strips oversized
InlineBinaryvalues nested in sequences. - On an affected series, metadata went from ~979 MB to ~336 KB, with every instance kept.
- Series and study metadata queries now drop any binary or private element larger than
- Streaming (#256): metadata is fetched in small Arrow batches and sent in batched chunks. The cursor is released immediately when a client disconnects.
- Event loop (#256): the gateway metrics reporter's Lakebase calls no longer block the event loop. The default interval is now 5 s (
DICOMWEB_METRICS_INTERVAL).
Changes
- Gateway runs two workers (#256):
app-config.ymlnow startsuvicornwith--workers 2, so one heavy request cannot block the others. Each worker keeps its own in-memory caches, so baseline memory roughly doubles. Set--workers 1to revert. - Viewer (#256): response gzip uses compression level 5 instead of 9.
src/dbx/pixels/version.pynow reports3.1.1.
Upgrade notes
- Redeploy the gateway and viewer apps (
deploy_gateway,deploy_viewerin the install job). No table migration. - Metadata responses no longer include binary or private elements larger than the threshold. Standard non-binary tags are unchanged. Raise
PIXELS_METADATA_INLINE_BINARY_MAXif a client needs larger inline values.
Note: this release is tagged on the
hotfix/3.1.x-series-metadatabranch (1f07637). The changes are merging tomainvia #256.
Full changelog: 3.1.0...3.1.1