Skip to content

Support pinned episode versions in streaming and topic APIs - #178

Draft
mguida22 wants to merge 1 commit into
mainfrom
guida/dc-2016-episode-pins
Draft

mguida22 wants to merge 1 commit into
mainfrom
guida/dc-2016-episode-pins

Conversation

@mguida22

@mguida22 mguida22 commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Episode reads currently default to the latest episode even when a caller has a committed dataset's pinned version. Add optional episode_version to iter_messages, download_data, and get_topics, forwarding it as episodeVersion. Omitting it preserves latest-version behavior; specifying it requires episode_id and works with explicit time bounds for lookback.

Validation: all 144 client tests pass; black, flake8, and pyright pass in the Python 3.8 CI environment. GitHub CI passes. Existing dataset download pin handling and membership deserialization already preserve versions.

Live verification against https://api.foxglove.party passed with the fixed SDK and disposable fixtures: pinned versus latest counts were 257 versus 157 after a time-window edit and 1,679 versus 126 after a recording-membership edit. Pinned content digests remained stable across repeated reads and replanning; explicit pinned topic discovery also passed. All temporary datasets/episodes were deleted and the supplied original artifacts remained unchanged.

Part of DC-2016. Keep draft. SDK integration depends on releasing this client support; no release version is assumed.

@linear-code

linear-code Bot commented Oct 29, 2026

Copy link
Copy Markdown

DC-2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant