xxsoul

Results 9 comments of xxsoul

> > 你的配置文件格式有误,参考 `config.example.cfg` 来写吧 > > 我就是复制的readme里的config.example.cfg呀,然后填写了参数,注释了password 配置文件那,‘mode = "browser"’的话走了浏览器登录,但是下面注了“password”并且放开了“session_token”,配置文件矛盾了 如果打算用session_token登录OpenAI的话,就设置’mode = ”browserless“‘,维持“password”和“email”的注释状态,例如: ``` [[openai.accounts]] mode = 'browserless' ... # email = "xxxx" # password = "xxx" ... session_token...

@magisk317 你是怎么部署的呢?是docker单独起镜像?还是docker-compose起的?还是单独运行的脚本或py项目? 看到错误信息【2023-02-24 18:32:39 chatgpt-chatgpt-1 | aiohttp.client_exceptions.WSServerHandshakeError: 404, message='Invalid response status', url=URL('http://mirai:8080/all?qq=*******&verifyKey=*******')】,似乎使用docker-compose启动的项目?

> 是的,docker-compose,三个镜像一起起的 错误信息看上去像是Mirai没有启动对应的服务或端口?建议跟着wiki里的文档配置下 https://github.com/lss233/chatgpt-mirai-qq-bot/wiki/%E4%BD%BF%E7%94%A8-Docker-Compose-%E9%83%A8%E7%BD%B2%EF%BC%88%E5%90%8C%E6%97%B6%E4%BD%BF%E7%94%A8-Mirai-%E5%92%8C-%E6%9C%AC%E9%A1%B9%E7%9B%AE%EF%BC%89#5-%E9%85%8D%E7%BD%AE-mirai-http-api 跟着wiki走一遍之后基本就能启动了

多用户是指多个OpenAI账户么? 可以考虑在```[[openai.accounts]]```中加个alias别名或干脆按配置顺序指定id,刷新session_token时按alias或者id刷新,毕竟手动刷新seesion_token的人和部署的人绝大概率是一个人或是了解明确配置的人,这个门槛也是比较容易接受的

issue3141 (https://github.com/go-kratos/kratos/issues/3141) The root cause of EncodeURL ignoring fields is that its internal encodeMessage function does not support encoding Message-type data and returns err, and the current revision process destroys...

@ranxuxin001 我们在1.28版本的k8s上成功调度起来了官方给的测试镜像,不过需要魔改代码,我们遇到的问题主要集中在对cgroup的魔改,当前的gpu-manager和vcuda-controller都是基于cgroup v1获取podUid,containerId和宿主机PID的,需要适配到cgroup v2上 ![image](https://github.com/user-attachments/assets/b02e69ca-4c69-4c82-b04c-ab1c1afd3a3f) ![image](https://github.com/user-attachments/assets/a4321c26-c5f4-45ce-9526-94c07c07076b)

The 'id' looks like the ‘busId’ of the graphics card device. ![image](https://github.com/user-attachments/assets/86e4470e-6ace-4056-94ca-9b7a6775f7a1)

Is the cgroup version used on the host machine v1 or v2? gpu-manager code uses the path of cgroup v1 to try to read the PID of the container process...