Repository navigation
English
- Network failures no longer stop at a bare
fetch failed: the underlying cause (for examplegetaddrinfo ENOTFOUND …,UND_ERR_CONNECT_TIMEOUT, or a TLS certificate code) is now shown without settingRNU_DEBUG=1. - DNS failures, connect timeouts, socket errors and untrusted-root TLS errors (common behind HTTPS-inspecting proxies) now get the network troubleshooting tips, which also mention
NODE_EXTRA_CA_CERTS. - When none of the API endpoints answers, the CLI now says the local network reaches none of them and suggests pinning a working one with
RNU_API, instead of silently falling back to the first endpoint.
中文
- 网络失败不再只显示
fetch failed:无需设置RNU_DEBUG=1,即会附带底层原因(如getaddrinfo ENOTFOUND …、UND_ERR_CONNECT_TIMEOUT或 TLS 证书错误码)。 - DNS 解析失败、连接超时、socket 错误以及根证书不受信任(常见于会替换 HTTPS 证书的代理)现在也会给出网络排查提示,并新增
NODE_EXTRA_CA_CERTS的说明。 - 所有 API 线路都探测失败时,CLI 会明确提示本机无法连接任何线路,并建议用
RNU_API指定可用线路,而不是静默改用第一条线路。
Full changelog: v2.29.4...v2.29.5