Skip to content
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

1.14: Two upstreams share the same priority #242

Open
PDVJAM opened this issue Jun 6, 2023 · 1 comment
Open

1.14: Two upstreams share the same priority #242

PDVJAM opened this issue Jun 6, 2023 · 1 comment

Comments

@PDVJAM
Copy link

PDVJAM commented Jun 6, 2023

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.

@AJolly
Copy link

AJolly commented Sep 7, 2023

Running into the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants