-
Notifications
You must be signed in to change notification settings - Fork 1
docs(adr): define TEPP topic-lineage consumption boundary (TRSL-TM + CHRONOS/TDT) #584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
85a3d53
docs(adr): define TEPP topic-lineage consumption boundary (TRSL-TM + …
seonghobae 9cf11fb
feat(analysis-run): add topic-lineage kind mirroring TEPP's fail-clos…
seonghobae 3b669d3
fix: enforce topic-lineage envelope contract and retire buyer wording
seonghobae ee2782e
feat(lineage): add evidence/inference/prediction status-mark primitive
seonghobae c289fc1
Merge remote-tracking branch 'origin/main' into fix/topic-lineage-bou…
seonghobae bd28a91
Merge remote-tracking branch 'origin/main' into fix/topic-lineage-bou…
seonghobae 17068ec
Merge remote-tracking branch 'origin/main' into codex/pr584-repair
seonghobae 2ea9bac
fix(topic-lineage): expose and validate TEPP results
seonghobae File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔍 Topic-lineage result read is not table-missing tolerant
The read of
analysis_run_topic_lineage_result(backend/app/analysis_run_ingestion.py:410-424) is not wrapped intry/except asyncpg.UndefinedTableError, unlikefetch_reconstructed_edgeswhich tolerates a missing migration-0021 table. A database with migration 0131 (the kind) but not 0132 (the result table) would 500 when opening a topic-lineage run detail. The seed script applies 0131 but not 0132 while creating such a run. AGENTS.md says app code must not compensate for a missing table, so this asymmetry may be intentional.Was this helpful? React with 👍 or 👎 to provide feedback.