lintsinghua / lintsinghua/DeepAudit

循环Bug

Open
#78 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7k
Forks
850
PR merge metrics
No merged PRs in 30d

Description

首先是 gemini 2.5 llm 连接测试为空,但其实能用,但是在跑的过程中一直循环。
![image-20251219003405813](https://blog-1308722180.cos.ap-guangzhou.myqcloud.com/image-20251219003405813.png)

然后是openai 官方密钥官方接口 gpt 5.1 无法正常调用工具
![image-20251219003328652](https://blog-1308722180.cos.ap-guangzhou.myqcloud.com/image-20251219003328652.png)
llm 启动的 minimax 也无法调用工具
![image-20251219003531226](https://blog-1308722180.cos.ap-guangzhou.myqcloud.com/image-20251219003531226.png)
目前唯一跑下来能正常跑完全流程的是 qwen3-next,但是漏了很多关键漏洞,基本上只关注到了 sql

Contributor guide

Open the contributing guide

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 files, tests, or entry points are identified. Start by reproducing the empty Gemini 2.5 connection test and looping run, then compare tool-calling behavior across the named providers; done means the affected providers complete the workflow without looping and tool calls work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.