kjh2064
a5493142f9
- docs/GITEA_TOKEN_HOME.md: 토큰 홈 설정 문서 업데이트 - docs/GITEA_TOKEN_HOME_RUNBOOK.md: 런북 보완 - docs/GITEA_VARIABLES_FAILURE_ANALYSIS.md: 실패 분석 문서 수정 - docs/GITEA_VARIABLES_RUNBOOK.md: 변수 런북 수정 - tools/validate_gitea_pr_harness_v1.py: PR 하네스 검증 스크립트 개선 - tools/validate_gitea_token_home_v1.py: 토큰 홈 검증 스크립트 개선
1.5 KiB
1.5 KiB
GITEA_TOKEN_TAXBAIK Runbook
1. Confirm presence
Check that GITEA_TOKEN_TAXBAIK is set in the shell that runs the harness.
2. Validate read-only access
python tools/validate_gitea_token_home_v1.py
Expected:
gate = PASS- repo access works
- workflow metadata is readable
3. Dispatch smoke test
python tools/validate_gitea_token_home_v1.py --dispatch --workflow kis_data_collection.yml --ref main
Expected:
- dispatch returns
204or201 - latest run is visible in the API
- run status becomes visible in the response payload
4. If it fails
GITEA_TOKEN_TAXBAIK missing or empty: environment is not configured401 Unauthorized: token is wrong or lacks repo scope404 Not Found: repo or workflow path mismatchlatest_run_missing: dispatch accepted, but run listing lagged behindqueuedor longin_progress: runner is busy or the job is waiting for the self-hosted runner slot
5. Evidence to capture
- Harness JSON output
- Workflow run URL
- Failing step name if the dispatched run fails
- Runner status from the API if the job stays queued
Current run 161 finding
Checkout Codefailed before Python started.- The repository checkout did not contain
GatherTradingData.json. - This means the next fix is not token-related; it is seed-file availability at workflow runtime.
- The workflow is now updated to regenerate the JSON from
GatherTradingData.xlsxwhen possible and to fail with explicit recovery instructions when both are missing.