Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When switching nodes, data from the previous connection can be used for new connection requests #2713

Open
myxmaster opened this issue Jan 7, 2025 · 0 comments
Labels
Bug Something isn't working

Comments

@myxmaster
Copy link
Contributor

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()?

this.aliasesById = {};
this.aliasMap.clear();
this.chanInfo = {};

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

@myxmaster myxmaster added the Bug Something isn't working label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant