Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Quorum Raft support broken in versions >5.1.50 #3958

Open
1 task done
bmcd opened this issue Mar 31, 2021 · 4 comments
Open
1 task done

Quorum Raft support broken in versions >5.1.50 #3958

bmcd opened this issue Mar 31, 2021 · 4 comments

Comments

@bmcd
Copy link

bmcd commented Mar 31, 2021

Also asked for help in the Consensys discord


Issue

Quorum support (raft) is broken in truffle since 5.1.50

Steps to Reproduce

You can run a simple 3-node local raft network with npx quorum-wizard -q (and then cd into the network directory and run the start script).
Set up a basic truffle project and config for a quorum network:

  networks: {
    development: {
      host: '127.0.0.1',
      port: 22000,
      network_id: '*',
      type: 'quorum',
      gasPrice: 0,
    },
  },

Then when you try to run npx truffle@5.2.6 migrate, it will get stuck waiting for the block to be confirmed. It does this all the way down to truffle@5.1.50

Expected Behavior

Truffle migrate correctly detects when the block is confirmed and moves onto the next step.

Actual Results

Truffle waits until it times out a 750 seconds, even though the transaction/block was successfully committed on chain.

npx truffle@5.1.49 migrate works, and all versions work when you use IBFT instead of raft for consensus. So it's probably related to the raft nanosecond timestamps.

Environment

  • Operating System: MacOS
  • Ethereum client: Quorum 21.1.0
  • Truffle version (truffle version): 5.1.50 to 5.2.6
  • node version (node --version): 14.16.0
  • npm version (npm --version): 7.6.0

Thanks!

@gnidan
Copy link
Contributor

gnidan commented Mar 31, 2021

Can you try upgrading to v5.3.0? The problem may be fixed. Thanks!

@bmcd
Copy link
Author

bmcd commented Apr 2, 2021

Looks like the issue still exists in 5.3.0

@gnidan
Copy link
Contributor

gnidan commented May 5, 2021

Looks like the issue still exists in 5.3.0

Darn. Well, guess we'll have to look into it!

Thanks for reporting this.

@danillosl
Copy link

any updates on this issue?

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

No branches or pull requests

3 participants