feat(etl): rebuild replay on refreshed cancellation stack - #256
Draft
seonghobae wants to merge 8 commits into
Draft
feat(etl): rebuild replay on refreshed cancellation stack#256seonghobae wants to merge 8 commits into
seonghobae wants to merge 8 commits into
Conversation
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks 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 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 repair
This Draft repairs the next invalid durable-job boundary without rewriting old PR #148. Its immediate predecessor is refreshed cancellation PR #254 at exact head
1fd2691dde1ebfd235c53703e6018eee11249f04; old #148 still targets the obsolete #147 branch and therefore cannot prove ancestry from the refreshed cancellation implementation. No #148 check, review, approval, status or synthetic-merge evidence transfers.TDD phase
Exact first head
121654bfa463f90e2d64222f9ca60f1750a33e0eadds onlyEtlJobReplayBoundaryTestfrom the preserved replay work. The test reaches the production replay boundary by requiringEtlJobReplayandEtlJobReplayService, which are intentionally absent on the refreshed cancellation ancestry. The required first hosted result is RED at missing replay production types/contract after normal production compilation; setup, dependency, fixture or runner failure does not qualify.After a valid RED, rebuild only the bounded replay production surface and then the persistence/state tests from #148 through auditable GREEN commits, proving exact file/semantic preservation before considering #148 superseded. Do not claim the larger obsolete #135 replay design, migrations, HTTP exposure or release semantics that #148 itself had not rebuilt.
No force-push, destructive rebase, ours/theirs shortcut, gate weakening, stale-evidence transfer, protection bypass or cross-repository write is permitted.