search

threefoldtech / tfgrid-sdk-ts

Apache License 2.0
4 stars 8 forks source link

🐞 [Bug]: Search by node id 88 error #3484

Open amiraabouhadid opened 1 month ago

amiraabouhadid commented 1 month ago

Is there an existing issue for this?

which package/s did you face the problem with?

Dashboard

What happened?

searching by node id in node finder produces error

Steps To Reproduce

  1. go to node finder
  2. search by node id 88
  3. look at error below in console

which network/s did you face the problem on?

Dev

version

current

Twin ID/s

No response

Node ID/s

No response

Farm ID/s

No response

Contract ID/s

No response

Relevant screenshots/screen records

image

Relevant log output

Error getting node object for node ID 88:  TypeError: Cannot read properties of undefined (reading 'last_deployment_timestamp')
    at fe (index-fb0b8f0b.js:378:74519)
    at async index-fb0b8f0b.js:378:72185
index-fb0b8f0b.js:16 Error getting node object for node ID 131:  AbortError: signal is aborted without reason
    at index-fb0b8f0b.js:43:2621
scottyeager commented 1 week ago

I'm seeing the second error appearing for a number of mainnet nodes:

Error getting node object for node ID 6869:  AbortError: signal is aborted without reason
    at index-fb0b8f0b.js:43:2621
Error getting node object for node ID 1256:  AbortError: signal is aborted without reason
    at index-fb0b8f0b.js:43:2621

This is when searching and opening node details in node finder. This error message also appears:

image

But the nodes are actually online.

mahendravarmayadala93 commented 3 days ago

I noticed this issue again for the Node : 3758 and it is up on the Gridproxy : https://gridproxy.grid.tf/nodes/3758/status

image
mahendravarmayadala93 commented 2 days ago

I observed this error on Node 6489, which last reported uptime on October 30, 2024, at 06:40:06 GMT+0000. The client is unable to reach this server as well.

image