Duplicate PeerStatus api call

[deekshithvarma256]

What happened?

For the network tab ledger height and the dashboard peer status, the same api is being called. But instead of calling it once, a duplicate api call is being made, making the api being hit two times consecutively. By these consecutive calls, one response gives the correct peer status, while the other response continuously gives the fetching status for the peers.

What did you expect to happen?

For the network tab ledger height and the dashboard peer status, the respective api should be called only once returning the correct peer status as response.

How can we reproduce it (as minimally and precisely as possible)?

1. Start the explorer.
2. Observe the dashboard peer status( green/red dots) and the network tab - ledger height.
3. Open inspect tab in the browser and observe the network tab filtering the 'peer' api. Observe that on every sync, a duplicate api call is being made and the response is incorrect for the same.
4. Stop one peer and repeat steps 2 & 3.
5. Stop one orderer and repeat steps 2 & 3.
6. Restart the peer and orderer. Observe in dashboard that the peer status shows 'fetching' continuously.

Anything else we need to know?

No response

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here