feat(api): inspect analysis-run retry parent from LineageWeave and Naruon - #396
Draft
seonghobae wants to merge 1 commit into
Conversation
…ruon
LineageWeave can GET /v1/analysis-runs/{run_id}/parent without a Naruon-labelled
exchange. NaruonLiveService serves the same metric-free inspect for Naruon only
and returns parent null on accepted creates. tepp-loopback proves a non-null
parent over TCP after create, cancel, and retry (ADR 0044).
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 31, 2026
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
1 participant
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.
Why
GAP-003A / issue #166 still has no LineageWeave retry-parent exchange builder, no Naruon compatibility-listener inspect, and no
tepp-loopbackTCP proof of a non-null parent. ADR 0038 / #384 addedGET /v1/analysis-runs/{run_id}/parentonAnalysisRunLiveServiceand the Naruon inspect builder only. A published LineageWeave consumer would have to mint a Naruon-labelled inspect.NaruonLiveServicestill refused every GET path.Live slices that this PR does not duplicate:
analysis_enginescientific-acceptance libraryc12ea6005c808fad36e782f5d175f7d85a28170e)What
Unique GAP-003A retry-parent consumer-parity slice stacked on #384 over protected main
1bc02f580cf48e1d39da239f0e818453437c31c3:lineageweave_analysis_run_retry_parent_exchangereuses the Naruon inspect builder and replaces onlytepp-consumerNaruonLiveServiceserves metric-free retry-parent GET for Naruon only; LineageWeave remains refused there"parent": null(200) because that listener does not retry; unknown, consumer mismatch, nonempty body, and metric keys fail closedtepp-loopbackcreate-cancel-retry-inspect over loopback TCP proves a non-null parent onAnalysisRunLiveServiceNot an ADR 0014 scientific claim. Not GET status. Not lifecycle POST. Not collection GET. Not retry POST. Not retry-lineage. Not persistence. Does not open
NaruonLiveServiceto LineageWeave. Does not add retry toNaruonLiveService.Verification
cargo clippy -p tepp_api --all-targets -- -D warningscargo test -p tepp_api --lib --testscargo doc -p tepp_api --no-depspython3 scripts/validate_documentation.pypython3 scripts/check_docstrings.pycrates/tepp_api/tests/lineageweave_http_contract.rscrates/tepp_api/tests/naruon_live_http_contract.rscrates/tepp_api/tests/loopback_binary_contract.rsdocs/research/analysis-run-retry-parent-consumer-parity.mdExact-head Checks on
02eee9f07f58dd6dee5396c36cfcd0a0b228d199are required before merge. Two independent current-head APPROVEs are required. Author cannot self-approve. Merge #384 before this stacked PR, or retarget onto protected main after #384 lands. No force-push.