bug: app fails to connect to local testnet on running on the same device, when the home WiFi drops

[happybeing]

This looks a bit weird but worth noting I think. I'm running a Ubuntu 24 laptop connected to WiFi hotspot on my phone for 4G mobile internet. The laptop is running the local testnet and the apps I'm testing, so in theory the connection to WiFi should not be relevant.

I've had a local testnet running for days, possibly weeks and been running lots of tests of two of my own apps against it. The apps uses code very similar to the latest code from ant-cli, copied and pasted into my apps.

Today my WiFi hotspot went off unexpectedly and I could no longer connect to the local testnet on the laptop, from the same laptop. Here's the error:

Dweb Autonomi client initialising...
⢀ Connecting to a local Autonomi Network...                                                                                                                   Failed to connect to the network: Failed to populate our routing table with enough peers in time
🔗 Failed to connect to the network                                                                                                                           The application panicked (crashed).
Message:  Failed to connect to Autonomi Network: 
   0: Failed to connect to the network: Failed to populate our routing table with enough peers in time

Location:
   /home/mrh/src/autonomi/dweb/dweb-lib/src/autonomi/actions/connect.rs:52

connect.rs is copied directly from ant-cli and has been working fine for days. As soon as I reconnect the laptop to the WiFi hotspot, the problem goes away.

Also worth noting in that the connect.rs code panics when it fails to connect which is not good!

[rreive]

first thing that comes to mind when I see panic is there is not enough memory to load the process/object, so that point to a slow structured memory leak showing up because otherwise rust takes care of garbage collect, so it must be a primary loop/used alot process/object ?

…

On Tue, 28 Jan 2025 at 14:05, Mark Hughes (happybeing) < ***@***.***> wrote: This looks a bit weird but worth noting I think. I'm running a Ubuntu 24 laptop connected to WiFi hotspot on my phone for 4G mobile internet. The laptop is running the local testnet and the apps I'm testing, so in theory the connection to WiFi should not be relevant. I've had a local testnet running for days, possibly weeks and been running lots of tests of two of my own apps against it. The apps uses code very similar to the latest code from ant-cli, copied and pasted into my apps. Today my WiFi hotspot went off unexpectedly and I could no longer connect to the local testnet on the laptop, from the same laptop. Here's the error: Dweb Autonomi client initialising... ⢀ Connecting to a local Autonomi Network... Failed to connect to the network: Failed to populate our routing table with enough peers in time 🔗 Failed to connect to the network The application panicked (crashed). Message: Failed to connect to Autonomi Network: 0: Failed to connect to the network: Failed to populate our routing table with enough peers in time Location: /home/mrh/src/autonomi/dweb/dweb-lib/src/autonomi/actions/connect.rs:52 connect.rs is copied directly from ant-cli and has been working fine for days. As soon as I reconnect the laptop to the WiFi hotspot, the problem goes away. Also worth noting in that the connect.rs code panics when it fails to connect which is not good! — Reply to this email directly, view it on GitHub <#2676>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACK3MFTO2P4DJOH4OF6KLBD2M7IH3AVCNFSM6AAAAABWBGFHZCVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAYTMNJQGM2TOMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Robert Reive zoom use this email for invite

[happybeing]

@rreive The code is designed to panic when it fails to connect.