Thread

🛡️
I've noticed this in the last few weeks so maybe its that: I'll need to debug further when it happen to Mr again. Are you still getting the same issue?
DanConwayDev's avatar DanConwayDev
`Relay::try_connect` is less reliable at establishing a connection than say nak, or other web based tools. Under certain network conditions, and with specific relays, `Relay::try_connect` will consistantly fail where nak will consistantly succeed (usually after a short delay <2s and the configured timeout). During these periods I can repeat the connection 10+ times. This hasn't been too noticable as connections to other relays pick up the slack but sometimes important events are only on that relay. I started noticing it with v0.43 but it may have been like this for a while. Have you noticed this? Next time this happens I'll try and investigate and debug further.
View quoted note →

Replies (2)

🛡️
Still happens every single time. I have no idea of what to do. It wasn't like that before, then it started happening without me changing anything. It also happens on other ngit/grasp codebases. Yesterday I updated ngit to the latest master to see if something was fixed, but the problem remained.
🛡️
↩ replying to fiatjaf
Do you get the same error with older versions of ngit? The last time rust-nostr changed the connection logic was v0.39 according to the change log and its on v0.44 now. I only noticed this as an intermittent problem in the last 2 weeks. It effected connecting to other relays but never all the repo relays at once. This makes me think its a rust-nostr/ngit ssue rather than a problem at the relay end. I bumped master to rust-nostr v0.44.1 yesterday.