fix(reliability): bound release-index Git metadata lookup on clean lineage - #715
fix(reliability): bound release-index Git metadata lookup on clean lineage#715seonghobae wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml 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 |
|
Closing this temporary replacement because #708 moved concurrently during queue cleanup and is now itself reconciled directly onto protected |
Controlled current-main replacement for #708
This is the clean-lineage replacement for stale/diverged Draft #708. It is based directly on protected
maind2301dccb7d39a794d08cc96ea8c858b9ff49125and carries only the already-proven release-index Git metadata timeout slice. #708 preserves the original fail-first history; its old-base checks/reviews do not transfer.Production boundary
scripts/build_release_evidence_index.py::_source_commitparticipates in acquisition/release evidence generation. A hunggit rev-parse HEADmust not stall that pipeline indefinitely.This branch:
GIT_METADATA_TIMEOUT_SECONDS = 5deadline;subprocess.TimeoutExpiredbefore the generic Git-unavailable fallback and fails closed with stable non-reflectiveRuntimeError("source commit lookup timed out");unknownfallback for ordinary non-timeout Git unavailability;No release-evidence schema, artifact digest, numerical code, dependency/workflow, version/release, provider/reviewer credential or canonical #604/#621 documentation change is included.
Verification boundary
Keep Draft until this unchanged head receives focused/full CI, Security Scan and SAST evidence against the current protected base, zero valid unresolved findings, and repository review/branch policy. The earlier #708 RED remains historical evidence only and is not treated as same-head acceptance.
Supersedes #708 after this replacement is opened and lineage is recorded.