OpenMOSS / OpenMOSS/MOSS

plague 版本貌似可能会选择不用工具,这该怎么继续下去呢?

Open
#181 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
12.3k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

image
如图,因为我把你们的网络插件部署到server端口的时候出了点问题(图里的报错),就像看看MOSS能不能解决我的问题: ),不过他直接回答了“<|Commands|>: None”导致下一步的检索过程没办法执行。这该怎么办呢?
(顺便一问,有不用docker的后端部署方法吗?虽然直接load你们的网络插件还挺快的(比加载模型快很多))

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the reported server deployment error shown in the attached image and checking the network-plugin/tool invocation path; done means the backend deployment and subsequent retrieval step proceed instead of returning “<|Commands|>: None”.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
ai, backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.