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

Does not properly close connections. #2

Open
garbados opened this issue Dec 24, 2017 · 0 comments
Open

Does not properly close connections. #2

garbados opened this issue Dec 24, 2017 · 0 comments

Comments

@garbados
Copy link
Owner

garbados commented Dec 24, 2017

Currently, the test suite for dat-friend fails due to timeout. When running DEBUG=* npm test I see:

dat-friend stop +5ms
dat-friend stopping root dat +1ms
dat-node leaveNetwork() +415ms
discovery-channel chan=67ed90..fb leave() +7ms
dns-discovery unannounce() 67ed907d93d98cda02241a4ec95e28b047a824f4 +49ms
bittorrent-dht [906635e] destroying +32ms
dat-friend stopping 95a964430e5a5c5203dde674a1873e51f2e8e78995855c1481020f405ee9a772 +4ms
dat-node leaveNetwork() +5ms
discovery-channel chan=67ed90..fb leave() +5ms
dns-discovery unannounce() 67ed907d93d98cda02241a4ec95e28b047a824f4 +5ms
bittorrent-dht [206e05e] destroying +4ms
dat-node Stream close +4ms
dat-node Stream close +1ms
dat-node Stream close +0ms
dat-node Stream close +0ms
dat-node Stream close +1ms
dns-discovery DNS query 188.166.107.197:5300 0Q 0A +1 +6ms
dns-discovery Announce received via SRV 67ed907d93d98cda02241a4ec95e28b047a824f4 67.189.104.224:peer.port +0ms
dat-node Stream close +2ms
dat-node Stream close +1ms
dat-node Stream close +1ms
dat-node Stream close +0ms
dat-node Stream close +0ms
dat-node Stream close +1ms
dat-node Stream close +0ms
bittorrent-dht [5eeca72] found node 67e2c1a532d371d5966cdd7141e807373de2d716 (target: 67ed907d93d98cda02241a4ec95e28b047a824f4) +55ms
bittorrent-dht [5eeca72] found node 67f147ac369bd178886abee631cbeca7a3535220 (target: 67ed907d93d98cda02241a4ec95e28b047a824f4) +101ms
bittorrent-dht [5eeca72] found node 67ec00142af8211a85f177f31bb1079ff272b38e (target: 67ed907d93d98cda02241a4ec95e28b047a824f4) +168ms
bittorrent-dht [5eeca72] found node 67ec6cd6ae529049f1f1bbe9ebb3a6db3c870ce1 (target: 67ed907d93d98cda02241a4ec95e28b047a824f4) +67ms
...

The swarm continues to communicate with these new peers until the test suite times out.

You can see that bittorrent-dht finds peers after dat-node has closed a number of streams. I can't find the problem in dat-node or discovery-swarm, and I hesitate to dive deeper in the dependency chain with no clue of what I'm doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant