You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears we've lost an API that tests latency to a single node. Single-node latency test doesn't work.
Another issue is that the current logic for testing all nodes is not the same as Mihomo's; Mihomo only responds with the result when all nodes' latencies are tested. However, it appears that clash-rs directly responds without waiting.
It appears we've lost an API that tests latency to a single node. Single-node latency test doesn't work.
Another issue is that the current logic for testing all nodes is not the same as Mihomo's; Mihomo only responds with the result when all nodes' latencies are tested. However, it appears that clash-rs directly responds without waiting.
See the video for what the issue means
QQ20260511-113527.mp4
API
/proxies/${encodeURIComponent(name)}/delayhttps://github.com/libnyanpasu/clash-nyanpasu/blob/main/frontend/interface/src/service/clash-api.ts#L126