-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soft migration to Generalize Multinode client for EVM BCI-2286 #11369
Conversation
dhaidashenko
commented
Nov 22, 2023
- Created feature flag that injects EVM client that is based on common/client/MultiNode
I see that you haven't updated any README files. Would it make sense to do so? |
# Conflicts: # core/chains/evm/client/chain_client.go # core/chains/evm/client/client.go # core/chains/evm/client/pool.go # core/chains/evm/client/send_only_node.go
func newEthClientFromChain(cfg evmconfig.NodePool, noNewHeadsThreshold time.Duration, lggr logger.Logger, chainID *big.Int, chainType commonconfig.ChainType, nodes []*toml.Node) (evmclient.Client, error) { | ||
var primaries []evmclient.Node | ||
var sendonlys []evmclient.SendOnlyNode | ||
func newEthClientFromCfg(cfg evmconfig.NodePool, noNewHeadsThreshold time.Duration, lggr logger.Logger, chainID *big.Int, chainType commonconfig.ChainType, nodes []*toml.Node) evmclient.Client { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we renamed this method?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method has no arguments with name or type chain (except chainID), so it felt weird to name it FromChain
.
But I do not mind renaming it back to the newEthClientFromChain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, sounds reasonable
* Allow switching to Generalized MultiNode EVM client via feature flag * test how linter reacts to deprecation * deprecate evm.client * address review comments * revert adding feature flag * create new client * fix call context * unwrapp CallContext args * deprecation msg improvements