chore(portfolio-deploy): make mainnet deployment more robust#12680
chore(portfolio-deploy): make mainnet deployment more robust#12680dckc wants to merge 5 commits into
Conversation
| // KLUDGE! avoid flaky load-balanced setup | ||
| rpcAddrMainGood = 'https://rpc.agoric-main-eu1.ccvalidators.com:443', |
There was a problem hiding this comment.
@Muneeb147 and I agreed that /network-config should take care of providing a working RPC node.
There was a problem hiding this comment.
Yes
Once SRE calls-out that main.agoric.net/network-config is providing stable rpcAddr, until then it's fine to use ccvalidators (as it's the same upstream which we use)
There was a problem hiding this comment.
I'm inclined to take this KLUDGE out before landing this PR.
If I see any more RPC trouble, I'll count on SRE to fix it by adjusting /network-config.
There was a problem hiding this comment.
I second it.
Let's rely on /network-config which points to main.rpc.agoric.net rpcAddr.
I have checked it is healthy as expected.
There was a problem hiding this comment.
But do have retries while hitting this rpc? Incase of any intermittent failure response...
dckc
changed the title
2 participants
Description / Upgrade Considerations
Security / Scaling / Documentation Considerations
n/a
Testing Considerations
https://github.com/Agoric/agoric-sdk/releases/tag/ymax-v0.3.2605-beta1 is an integration test
along with several runs up to https://github.com/Agoric/agoric-sdk/actions/runs/26269136326/job/77318699362