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

API node/status - invalid networkHeight #3533

Closed
4miners opened this issue May 7, 2019 · 1 comment
Closed

API node/status - invalid networkHeight #3533

4miners opened this issue May 7, 2019 · 1 comment
Assignees
@ManuGowda
Labels
type: bug

Comments

@4miners
Copy link
Contributor

4miners commented May 7, 2019 •
edited
Loading

Expected behavior

networkHeight should be always correct.

Actual behavior

networkHeight is incorrect (for about 1 second) when API called just after forging a block.

Screen Shot 2019-05-07 at 11 26 09

Steps to reproduce

Tested on a network with 10 nodes, all of them are on the same height and moving forward, the cache was disabled.
Call API endpoint http://lon1-foonet-000.liskdev.net:4000/api/node/status frequently and observe the results.

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

2.0.0-alpha.0
@4miners 4miners mentioned this issue May 9, 2019
Closed
@ishantiw ishantiw mentioned this issue May 10, 2019
Merged
@ishantiw ishantiw self-assigned this May 10, 2019
@MaciejBaj MaciejBaj assigned 4miners and unassigned diego-G and ishantiw May 15, 2019
@ManuGowda ManuGowda assigned ManuGowda and unassigned 4miners May 20, 2019
@ManuGowda
Copy link
Contributor

This issue is fixed and verified in alpha.8 tag
Screen Shot 2019-05-20 at 11 41 12

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ManuGowda ManuGowda

Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@diego-G @ManuGowda @ishantiw @4miners