search

paritytech / eng-automation

0 stars 0 forks source link

[EngAut] Re-initialize metadata on metadata version change #3

Closed lovelaced closed 5 months ago

lovelaced commented 2 years ago

As it stands now, if there is a runtime upgrade on-chain and the metadata breaks, the faucet also stops working until it is manually restarted when presumably it reloads the metadata. The version of the runtime is available on-chain and therefore this should be something that can be checked for and reloaded if necessary. This is probably the biggest issue with the faucet at the moment.

### Where to implement
- [ ] https://github.com/paritytech/polkadot-testnet-faucet/issues/223
- [ ] https://github.com/paritytech/eng-automation/issues/5
- [x] Tip Bot
- [x] V Bot
mordamax commented 1 year ago

Related: https://github.com/paritytech/polkadot-testnet-faucet/issues/223

mutantcornholio commented 1 year ago

Presumably, fixed. Moved the issue to "Blocked". Let's monitor it for a while.

mordamax commented 8 months ago

https://github.com/polkadot-js/api/blob/2d26e748f0e28a1d30ecb589eded677385476855/packages/api/src/base/Init.ts#L246C14-L246C22 this is probably the reason why with WS and explicit reconnection it doesn't re-load meta-data. And that's why the hard-restart of application helps. Basically if it'd be possible with disconnect to set this to false - may be it'd help

Or we just hard-start app

mordamax commented 5 months ago

No updates from last week

mutantcornholio commented 5 months ago

Deployed autorestart for faucet: https://github.com/paritytech/polkadot-testnet-faucet/issues/223

mutantcornholio commented 5 months ago

Deployed autorestart for chain-wide-payouts