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
kimi cli 的 login功能不支持 HTTPS_PROXY, https_proxy, no_proxy 这种环境变量导入的代理 || kimi cli's login function does not support HTTPS_PROXY, https_proxy, no_proxy and other proxies imported by environment variables.
#1690
At present, several different developers have encountered the same problem and submitted similar PRs to fix it: #1479, #1465, #1236 The project maintainers seem to ignore these PRs.
Can you please ask the relevant kimi-cli official students to explain whether this change does not comply with your roadmap or the related implementation does not comply with your development specifications? Without further communication, those of us developers who use intranet proxies in enterprises will be very troubled and don't know how to use kimi-cli more directly.
At present, every time I update the version, I use the branch where I repaired https_proxy and use rebase to a specific release version for local installation and use.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
目前好几个不同的开发者遇到相同问题都提了类似的PR修复了:#1479, #1465, #1236 项目维护者似乎无视这些PR。
能否请相关 kimi-cli 官方的同学来说明一下这个改动是否不符合你们的 roadmap 或者相关实现不符合你们开发规范?如果没有进一步交流,我们这些在企业里用内网代理的开发者会很困扰,不知道如何才能够更加直接地使用 kimi-cli。
目前我都是每次更新版本都是用我修复 https_proxy 的分支使用 rebase 到特定 release 版本之上进行本地安装使用。
之前的相关讨论:#916
At present, several different developers have encountered the same problem and submitted similar PRs to fix it: #1479, #1465, #1236 The project maintainers seem to ignore these PRs.
Can you please ask the relevant kimi-cli official students to explain whether this change does not comply with your roadmap or the related implementation does not comply with your development specifications? Without further communication, those of us developers who use intranet proxies in enterprises will be very troubled and don't know how to use kimi-cli more directly.
At present, every time I update the version, I use the branch where I repaired https_proxy and use rebase to a specific release version for local installation and use.
Previous related discussions: #916
Beta Was this translation helpful? Give feedback.
All reactions