Get syncing info always return null about moonbeam-docs HOT 5 CLOSED

Hey @AsceticBear I think this PR fixed the issue: polkadot-evm/frontier#630 - so I'll close this one

from moonbeam-docs.

Hey @AsceticBear, so according to: https://web3js.readthedocs.io/en/v1.5.2/web3-eth-subscribe.html#subscribe-syncing

...
"data" returns Object: Fires on each incoming sync object as argument.
"changed" returns Object: Fires when the synchronisation is started with true 
...
Object|Boolean - The syncing object, when started it will return true once or when finished it will return false once.

So if it returns empty is because that node is already synced, or there is no state change let's say.

When doing the same against a syncing Geth node the main difference is that the Geth node opens the port for connection, looks for peers and then starts syncing. This provides the necessary state change for it to return the following object:

true
{
  syncing: true,
  status: {
    StartingBlock: 0,
    CurrentBlock: 907507,
    HighestBlock: 0,
    PulledStates: 4503379,
    KnownStates: 4503379
  },
  startingBlock: undefined,
  currentBlock: undefined,
  highestBlock: undefined
}

Once the Geth node is done syncing, it will return a false object like the one shown above for Moonbeam.

from moonbeam-docs.

So if it returns empty is because that node is already synced, or there is no state change let's say.
Once the Geth node is done syncing, it will return a false object like the one shown above for Moonbeam.

If I understand correctly when we query sync status to a node that already synced, the expected output should be:

{
  syncing: true,
  status: false,
  startingBlock: undefined,
  currentBlock: undefined,
  highestBlock: undefined
}

However, when I tried to query sync status, the output is hanging after print 0x44546f334c704d6d6e356e4c41727a76. Can you get the output like the doc's show? or my test script is wrong?

from moonbeam-docs.

I have tested to set up fresh node to sync already running chain node, then query sync status, the result is empty as well. Perhaps you can try it out if you have are interested.

from moonbeam-docs.

I don't think Substrate nodes to have a initiation phase where the WS endpoint is open so eth_syncing returns a response, and when the actual synchronization starts happening (like on Geth).

When your node is in a syncing state and it is synced it should return false. I've opened an internal ticket as I found that we don't fully follow the behavior I got while reproducing in Geth.

I'll let you know once we have more info

from moonbeam-docs.