You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was switching to a regtest LND node (10.0.2.2:8085) with just 2 channels and noticed multiple (more than 100) time outs like this: Request timed out for: https://10.0.2.2:8085/v1/graph/node/038a82d6518d9f8bbd6ca6f0c7e4b0d8fe339252e454fe5f605b6a75baf2344152
-> all with different pub keys
I was coming from a CLNRest testnet node with lots of channels, and it is pretty clear that all those pub keys are coming from that CLNRest node. That means, we are not properly resetting data.
To reproduce, you need to connect to the CLNRest node and immediately switch to a different node, before all the backend calls for the CLNRest connection can finish.
Not the solution, but kind of related: Should we also clear those in ChannelsStore.ts:reset()?
Describe the bug
I was switching to a regtest LND node (10.0.2.2:8085) with just 2 channels and noticed multiple (more than 100) time outs like this:
Request timed out for: https://10.0.2.2:8085/v1/graph/node/038a82d6518d9f8bbd6ca6f0c7e4b0d8fe339252e454fe5f605b6a75baf2344152
-> all with different pub keys
I was coming from a CLNRest testnet node with lots of channels, and it is pretty clear that all those pub keys are coming from that CLNRest node. That means, we are not properly resetting data.
To reproduce, you need to connect to the CLNRest node and immediately switch to a different node, before all the backend calls for the CLNRest connection can finish.
Not the solution, but kind of related: Should we also clear those in ChannelsStore.ts:reset()?
Reproduce
...
ZEUS version
v0.9.5
Node interface
Multiple (specified in comments)
Network
Clearnet
Device
Pixel 7 Pro emulator
Device operating system
Android 14
Log output
No response
The text was updated successfully, but these errors were encountered: