Yu Hao Dong

自建的话我建议直接用geph5，目前geph4-client我已经改成了套geph5-client的一个非常薄的一个壳，很快会完全淘汰了

This is now fixed. The problem was that the Dialer got cloned out of the Mutex before the threads were spawned.

Unfortunately, this seems to still be an issue, though it appears after longer runs than previously and mostly on Android: 

My current guess is that occasionally, refreshing bridges from the broker *hangs indefinitely*. This can be seen by logs that show much more than 1000 seconds (the RefreshCell interval) without...

This still *occasionally* breaks when OS sleeping is involved, probably due to `Instant` not advancing as expected. So the latest version simply forces a refresh if the value in the...

This is still *somewhat* buggy: from Iran: ``` 2024-11-15T07:00:26 [DEBG]: opening tunnel remote_addr=udp$1.1.1.1:53 2024-11-15T07:00:52 [WARN]: individual client thread failed err=inner connection to 3.71.166.84:36627 failed Caused by: Connection reset by peer...

This should all now be fixed.

This *still* seems buggy.

Somehow, the Display implementation of a `Name` in `simple_dns` is buggy and could return errors spuriously. This seems to be due to, ultimately, this incorrect implementation of Display for `Label`:...

An attempt at a workaround: https://github.com/geph-official/geph5/commit/2556396434c3bbd7b73a536e8eacf0969579c785