Repository navigation
ingest: publish the committed dataset for the staff dashboard - #785
Open
AnikethCheluva wants to merge 1 commit into
Open
AnikethCheluva wants to merge 1 commit into
AnikethCheluva wants to merge 1 commit into
Conversation
Each round of the ingest loop now writes pipeline/dataset.json to the ingest bucket: every row of changes.lance, newest first, with the recordings table version its tag pins, plus that table's current version and row count. The dashboard already reads the ingest bucket and nothing else, so it can show staff each commit, the version it made and the recordings it added or replaced without reading Lance itself. It runs every round, not only after a loop commit, so a manual lance_commit --replace shows up too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack context
Follow-ups to the Lance ingest stack (#756–#761, then #770–#780). Stacked on #784.
Why
Staff review on the research workbench (Staff deliveries) ends at
committed. Staff could not see what happened in Lance after that: which commit took a delivery, the tag and table version it made, or whether a correction replaced a recording.The dashboard reads only the ingest bucket, and should not need Lance or R2 access to
rldb. So each round of the ingest loop (egomimic.ingest.run) now writespipeline/dataset.jsonto the ingest bucket. It holds:changes.lance, newest first: tag, source, operator, added, replaced, committed_atrecordings.lanceversion each commit's tag pinsIt is written every round, not only after a commit by the loop, so a manual
lance_commit --replaceshows up within one round. A failure to write it is reported in the round's log line and does not stop the loop.Tests
test_the_dataset_record_lists_each_commit_with_its_version: empty before the first commit; after one, the commit lists the recording as added and the version matches the tag; it round-trips through the store. Watch, store and tools tests: 133 passed on rl2-3.🤖 Generated with Claude Code