Share treasury executor pass runner#904
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR refactors ChangesExecutor logging refactor
🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
catcherintheroad-hub
left a comment
There was a problem hiding this comment.
Reviewed current head 158afa0652f5f2e7fac4487023215378c8f300b1 as a non-author.
Evidence checked:
- inspected
scripts/treasury_executor.pyandtests/test_treasury_executor_script.py; - confirmed
_run_logged_pass()centralizes the existing try/log-success/log-exception pattern while preserving--oncefailure exit behavior for treasury execution; - confirmed board refresh failures remain swallowed in the continuous loop and the new regression covers a failed refresh at 60s followed by another refresh attempt at 120s;
- verified the diff is limited to the treasury executor script and its focused test;
- checked GitHub state before review: PR open,
mergeable=MERGEABLE, CodeRabbit successful, no prior human reviews, and no #838 claim for PR #904 visible on the bounty issue.
Validation run on this exact head:
uv run --python 3.12 --extra dev python -m pytest tests/test_treasury_executor_script.py -q-> 9 passed.uv run --python 3.12 --extra dev python -m pytest tests/test_treasury_executor_script.py tests/test_treasury_executor.py -q-> 17 passed.uv run --python 3.12 --extra dev ruff check scripts/treasury_executor.py tests/test_treasury_executor_script.py-> passed.uv run --python 3.12 --extra dev ruff format --check scripts/treasury_executor.py tests/test_treasury_executor_script.py-> 2 files already formatted.uv run --python 3.12 --extra dev mypy scripts/treasury_executor.py-> success.uv run --python 3.12 --extra dev python scripts/docs_smoke.py-> docs smoke ok.git diff --check origin/main...HEAD-> clean.git merge-tree --write-tree origin/main HEAD-> clean treec76e9e40c1bf82f4135bdec79c20dc3d49a01461.
No blocker found in the focused maintainability refactor. Caveat: GitHub still reports mergeStateStatus=UNSTABLE because the hosted rollup currently only shows CodeRabbit; I did not see the full hosted Quality/readiness/docs/image check on this PR yet. Scope remains treasury executor logging/test behavior only; no proposal execution semantics, payout, ledger mutation, wallet behavior, admin-token behavior, private data, exchange, bridge, cash-out, or MRWK price behavior changed.
szx19970521
left a comment
There was a problem hiding this comment.
Reviewed PR #904 at current head 158afa0652f5f2e7fac4487023215378c8f300b1.
Evidence checked:
- inspected
scripts/treasury_executor.pyandtests/test_treasury_executor_script.py; - confirmed
_run_logged_pass()preserves the treasury executor--oncefailure path by returning1whenrun_once()raises; - confirmed continuous-loop board refresh failures remain logged and non-fatal, with the next refresh still scheduled;
- confirmed the refactor keeps the existing JSON-sorted success log shape for executor and board-refresh reports;
- checked GitHub state before review: this is not my PR, PR is open, mergeable, and the current head is
158afa0652f5f2e7fac4487023215378c8f300b1.
Validation on the reviewed head:
python -m pytest tests\test_treasury_executor_script.py -q-> 9 passed.python -m ruff check scripts\treasury_executor.py tests\test_treasury_executor_script.py-> passed.python -m ruff format --check scripts\treasury_executor.py tests\test_treasury_executor_script.py-> 2 files already formatted.python -m mypy scripts\treasury_executor.py-> success.
Scope reviewed: treasury executor pass logging/refactor and focused regression coverage only. No wallet material, ledger mutation, treasury proposal execution, payout execution, admin-token behavior, secrets, bridge/exchange/cash-out behavior, or MRWK price behavior was used.
Errordog2
left a comment
There was a problem hiding this comment.
Reviewed the treasury executor pass-runner sharing refactor.
Validation performed locally:
.venv\Scripts\python.exe -m pytest tests/test_treasury_executor_script.py-> 9 passed.venv\Scripts\python.exe -m ruff check scripts/treasury_executor.py tests/test_treasury_executor_script.py-> passed.venv\Scripts\python.exe -m ruff format --check scripts/treasury_executor.py tests/test_treasury_executor_script.py-> passed.venv\Scripts\python.exe -m mypy scripts/treasury_executor.py-> passedgit diff --check-> passedgit merge-tree $(git merge-base origin/main HEAD) origin/main HEAD-> clean merge
The extracted _run_logged_pass preserves the existing once-mode failure behavior for executor passes, keeps continuous-mode board refresh failures non-fatal, and the added test covers retrying after a board refresh exception. Looks good to me.
|
Closing this stale PR because its referenced bounty is no longer live/payable and the branch is dirty or unstable against current |
Bounty #846
Summary
_run_logged_pass()helper for treasury executor pass and bounty-board refresh logging/error handlingDuplicate check
gh search prs treasury_executor --repo ramimbo/mergework --state open-> no resultsgh search prs "bounty board refresh" --repo ramimbo/mergework --state open-> no resultsgh search prs "treasury executor" --repo ramimbo/mergework --state open-> only unrelated feat: implement MCP resource for public bounty board data #791 #828 public bounty-board MCP resource workValidation
.\.venv\Scripts\python.exe -m pytest tests\test_treasury_executor_script.py -q-> 9 passed.\.venv\Scripts\python.exe -m pytest tests\test_treasury_executor_script.py tests\test_treasury_executor.py -q-> 17 passed.\.venv\Scripts\python.exe -m ruff check scripts\treasury_executor.py tests\test_treasury_executor_script.py-> passed.\.venv\Scripts\python.exe -m ruff format --check scripts\treasury_executor.py tests\test_treasury_executor_script.py-> 2 files already formatted.\.venv\Scripts\python.exe -m mypy scripts\treasury_executor.py-> successgit diff --check-> cleanScope: maintainability-only cleanup in the read/write scheduler wrapper. No proposal execution semantics, bounty board payloads, ledger behavior, wallet behavior, treasury mutation rules, payout behavior, admin-token behavior, private data, exchange, bridge, cash-out, or MRWK price behavior changed.
Summary by CodeRabbit
Refactor
Tests