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

Confirmations value in block is NaN #3688

Closed
ManuGowda opened this issue May 21, 2019 · 1 comment
Closed

Confirmations value in block is NaN #3688

ManuGowda opened this issue May 21, 2019 · 1 comment
Assignees

Comments

@ManuGowda
Copy link
Contributor

Expected behavior

confirmations value should be valid and an integer and also the

Actual behavior

There are two issues here one is undefined value MONITOR: undefined
and another is confirmations value is undefined

MONITOR: undefined -> chain:blocks:change { id: '10705954266938328476',
      version: 1,
      timestamp: 94239710,
      height: 8305141,
      previousBlock: '9592550440812684133',
      numberOfTransactions: 0,
      totalAmount: 0,
      totalFee: 0,
      reward: 300000000,
      payloadLength: 0,
      payloadHash:
       'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855',
      generatorPublicKey:
       'a6b504812068c9a1186034966868118e1d98e88bc60835a81252f51136c3cddd',
      generatorId: '11027108891413363651L',
      blockSignature:
       'fccdec62363f37456174362d6857075209ea9bc2d1d50d30d6fff59771ac9c84cb86f3b032e0ac3bc9f26c67d47480a75019f712b1ff5834371eb794fb94d70f',
      confirmations: NaN,
      totalForged: '300000000',
      transactions: [] }

Steps to reproduce

Sync 2.0.0-alpha.9 node with testnet

Which version(s) does this affect? (Environment, OS, etc...)

2.0.0

@pablitovicente
Copy link
Contributor

For the undefined issue we have a different report in #3545 will work it in there

shuse2 added a commit that referenced this issue May 22, 2019
…k-is-nan

Confirmations value in block is NaN - Close #3688
@shuse2 shuse2 closed this as completed May 22, 2019
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