emeraldpay / emeraldpay/dshackle

1.14: Two upstreams share the same priority

Open
#242 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
350
Forks
57
PR merge metrics
No merged PRs in 30d

Description

Upgraded to 1.14 and see the following in logs:
```
2023-06-06 15:23:52.964 | WARN | PriorityForkChoice | Two upstreams share the same priority. It can cause an unpredicted behaviour of the Dshackle. Check config for alchemy and infura, both have 10 priority
```

But the config is actually has different priorities for alchemy and infura upstreams:
```
- id: alchemy
chain: ethereum
role: secondary
priority: 20
options:
disable-validation: true
validation-interval: 60
connection:
ethereum:
rpc:
url: "https://eth-mainnet.g.alchemy.com/v2/${ALCHEMY_KEY}"
- id: infura
chain: ethereum
role: primary
priority: 10
options:
disable-validation: true
validation-interval: 60
connection:
ethereum:
rpc:
url: "https://mainnet.infura.io/v3/${INFURA_DA_USER}"
ws:
url: "wss://mainnet.infura.io/ws/v3/${INFURA_DA_USER}"
```

Seems like a small bug.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.