[Bug] lumielle_echo v0.2.1 显示 Rejected,但重新检查返回 409“已有插件版本正在审核”
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the retry-review API endpoint for plugin versions and inspect how it checks review tasks, version status, and review locks. Then compare the backend state and logs for plugin version 0.2.1 with the state shown in the versions page; done means identifying why the request returns 409 and restoring safe retries if no review is still running.
Written by the indexing model from the issue text.
Description
问题概述 / Summary
微光回响(Lumielle-BlueOMOcean / lumielle_echo)v0.2.1 在页面显示 Rejected / LLM Guard,但点击“重新检查”被后端以 HTTP 409 拒绝,提示已有插件版本正在审核。刷新后仍显示 Rejected,无法恢复重检。
复现步骤 / Steps to reproduce
- 登录 AstrBot Cloud,打开下方插件页面的“版本”页。
- v0.2.1 显示 Rejected / LLM Guard,并提示“自动安全检查失败,已停止重试。请稍后重新提交;如问题持续,请联系管理员。”
- 点击 v0.2.1 的“重新检查”(按钮未禁用)。
- 浏览器 Network 显示
retry-review请求已发出,返回 HTTP 409,响应如下。 - 只读刷新页面后,v0.2.1 仍为 Rejected;页面同时可见 v0.2.0 为 Withdrawn / Manual Review、v0.1.0 为 Published / LLM Guard,没有可见的 Pending / Reviewing 版本。
本次诊断只对现有 v0.2.1 点击重检一次并刷新一次,没有撤销版本或提交新版本。
期望行为 / Expected behavior
请管理员核查该插件的实际审核任务、版本状态和可能未释放的审核锁:
- 若确有仍在运行的审核任务,请让前端显示实际状态,并说明应等待哪一版本的任务。
- 若任务已经失败或终止,请修复残留的占用/状态,使 现有 v0.2.1 可以重新安全检查。
插件版本希望先保持 0.2.1,不通过撤销版本或额外升号绕过此冲突。不请求跳过安全检查或直接批准发布。
实际行为 / Actual behavior
页面提示:
自动安全检查失败,已停止重试。请稍后重新提交;如问题持续,请联系管理员。
请求地址:
https://cloud.astrbot.app/api/v1/market/plugins/lumielle-blueomocean-lumielle-echo-af68b884120d60c9/versions/0.2.1/retry-review
HTTP 状态:409 Conflict
完整 JSON 响应:
{"code":409,"msg":"已有插件版本正在审核,请等待完成后再提交","data":null}
目前只能确认“页面显示终止状态,但后端拒绝重检并认为有版本正在审核”,具体是活跃任务、状态不同步还是残留审核锁,需要后台日志确认。
相关页面或资源链接 / Related URL
- 插件版本页:https://cloud.astrbot.app/plugin/Lumielle-BlueOMOcean/lumielle_echo?returnTo=/profile&tab=versions
- 插件源码:https://github.com/Lumielle-BlueOMOcean/astrbot_plugin_lumielle_echo_release
- v0.2.1:https://github.com/Lumielle-BlueOMOcean/astrbot_plugin_lumielle_echo_release/releases/tag/v0.2.1
AstrBot Cloud 版本或环境 / Version or environment
- AstrBot Cloud 官网,站点版本号未显示。
- Google Chrome / macOS。
- 插件:lumielle_echo,版本 0.2.1。
- 取证时间:2026-11-10 20:09:57(Asia/Shanghai,UTC+08:00)(UTC 原始记录:2026-11-10T12:09:57.054Z)。
日志、截图或其他上下文 / Logs, screenshots, or context
截图为刷新后仍显示 Rejected 的状态,已排除浏览器标签栏、Token、Cookie 等敏感信息。
提交前确认 / Checklist
- 已搜索该仓库现有 issue,未发现同一反馈;也核对了本账号没有重复提交。
- 已移除密码、Token、Cookie 等敏感信息。
- Dominant language
- No language data
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AstrBotDevs/astrbot-cloud-issues
-
[Bug]Openbug
Difficulty 3/5 1-2 days Newbie friendliness 46/100
-
[Bug] 自动安全检查失败Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
给我解封吧求求了,我再也不乱发插件了Open
Difficulty 1/5 Under an hour Newbie friendliness 5/100
AstrBotDevs/astrbot-cloud-issues#32 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
[Bug]Openbug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
AstrBotDevs/astrbot-cloud-issues#29 · 2 comments ·
All issues in AstrBotDevs/astrbot-cloud-issues
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
progress-deadline annotation accepts "0s" although validation says it must be positivePossibly taken @BahaaMattar claimed this today. Openarea/API kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
area:plugins kind:perf priority:p3 ready
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
api cleanup
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day