Conversation
|
I found some issues at enfein/mieru@deee7cb:
For Could we consider passing the domain name directly to the dialer when the TCP underlying layer doesn't provide a resolver, or providing a special |
|
We can add two more fields to the When they are enabled, |
|
After we add go1.26rc1 to test, we found mieru inbound test frequently failed on windows: https://github.com/MetaCubeX/mihomo/actions/runs/20403417598/job/58630963138#step:8:835 https://github.com/MetaCubeX/mihomo/actions/runs/20403417598/job/58629191794#step:8:837 https://github.com/MetaCubeX/mihomo/actions/runs/20396854396/job/58614005546#step:7:928 https://github.com/MetaCubeX/mihomo/actions/runs/20396854396/job/58613579605#step:8:838 There may still be undiscovered race issues in the existing code. |
|
The latest test also captured a crash: https://github.com/MetaCubeX/mihomo/actions/runs/20403417598/job/58630027679#step:8:827 |
|
I tested this commit: enfein/mieru@26af2fc, and it did not solve the problem. |
|
From the runtime stack, there is some problems with Are those issues only seen in go1.26? How often do you see that? |
|
In fact, due to the excessively frequent failures in version 1.26, we have already disabled the mieru inbound test in version 1.26, so we don't know if there are any more cases. |
Changes from the previous release:
DNSResolveris now a mandatory field in client config if you want to resolve proxy server domain name. Resolution happens when the underlay connection is created.Accept()is guaranteed to have user name information associated with it.