fix(core): harden dev NAV cron reconciliation (BRIX-1741)#253
Open
quay-worker[bot] wants to merge 1 commit into
Open
fix(core): harden dev NAV cron reconciliation (BRIX-1741)#253quay-worker[bot] wants to merge 1 commit into
quay-worker[bot] wants to merge 1 commit into
Conversation
Contributor
🔎 Lint report:
|
| Rule | Count |
|---|---|
unresolved-import |
1 |
First entries
tests/scripts/test_install_dev_nav_cron.py:8: [unresolved-import] unresolved-import: Cannot resolve imported module `pytest`
✅ Fixed issues: none
Unchanged: 5058 pre-existing issues carried over.
Diagnostics are surfaced as warnings — this check never fails the build.
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.
Summary
$HERMES_HOMEscript and cron record after install.--verifyand--run-nowmodes so operators can prove the host-state job exists and execute the exact materialized publish path for an on-chain freshness update.Deployment Steps
aws, Foundrycast,SEPOLIA_RPC_URL, a dedicatedDEV_NAV_PUBLISH_ACCOUNTorDEV_NAV_PUBLISH_KEYSTORE,DEV_NAV_PUBLISH_PASSWORD_FILE, and eitherDEV_NAV_PRICE_WEIor a prod RPC env var available in$HERMES_HOME/.env.python3 scripts/install_dev_nav_cron.pyon the Hermes host.python3 scripts/install_dev_nav_cron.py --verifyandhermes cron list; confirm exactly one enableddev-nav-sepolia-daily-publishjob appears.python3 scripts/install_dev_nav_cron.py --verify --run-nowto publish through the installed cron script path.cast call 0x3dBe8d456198B63d46703bbf8f46778B2922c825 "lastNavUpdate()(uint256)" --rpc-url "$SEPOLIA_RPC_URL"and confirm it matches the publish output timestamp.Verify the job remains scheduled at
30 6 * * *UTC after the immediate run.Test Plan
Pre-merge checklist
/home/hermes/.hermes/hermes-agent/venv/bin/python -m py_compile scripts/install_dev_nav_cron.py tests/scripts/test_install_dev_nav_cron.py$HERMES_HOMEsmoke: install then--verifysucceeds without touching live host state.$HERMES_HOMEsmoke: duplicate owned jobs are collapsed to one deterministic no-agent job.scripts/run_tests.sh tests/scripts/test_install_dev_nav_cron.py(blocked locally because the configured fallback venv does not havepytestinstalled).Post-deployment verification
python3 scripts/install_dev_nav_cron.py --verifysucceeds on the Hermes host.hermes cron listshows the enableddev-nav-sepolia-daily-publishjob targeting the installed script.python3 scripts/install_dev_nav_cron.py --verify --run-nowlands a Sepolia transaction and prints the publish timestamp.lastNavUpdate()on0x3dBe8d456198B63d46703bbf8f46778B2922c825returns the fresh timestamp from the publish output.