Repository navigation
test(go): 修正 #756 三项公开测试前置条件与重试断言(待全量验证) - #770
Merged
Merged
Conversation
Keep successful assistant responses non-retryable, make synthetic router affiliate codes unique, and scope BI01 credit units to its test. Full Go qualification remains unexecuted. The three private boundary failures and issue 757 remain unresolved.
5 tasks
Member
Author
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
7 tasks
20 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LMM API Pull Request
变更说明 / Summary
这是部分修复的 Draft PR,不是 #756 的验收通过记录。三项安全边界失败尚未归因,完整 Go 测试、go vet 和本地发布证据仍未完成。不要据此合并发布或关闭 #756。
已先阅读 #756 现有失败证据、
.github/SECURITY.md、仓库贡献规则和相关实现。原 Issue 的六项失败记录仅覆盖2e495ecadba8bcbfaf34fc3cee99bec9dda1db14,本 PR 不把该记录当成本轮结果。代码基准:
e1d04c82dbfcd6111cf7e94713fd079084414299,创建提交前重新读取的 main。初次检查时 main 为da5d16386f075a5dcc7cbc4746eba3b569af5ece;比较确认两者仅有前端变化,相关 Go 源码未变。本次提交:
349223f91461b5b245267e8df9f0efb0be99118f。仅修改三个
_test.go文件。以下归因来自 Issue 的旧失败证据及当前源码核对,尚未通过本轮运行确认修复结果。保留全部原顶层测试名称,没有添加跳过逻辑。BI01 的六组固定金额、钱包与 Token 余额、渠道用量、消费日志、重复结算及退款断言均保留;路由校验断言没有变更。生产源码、数据库结构、权限与资金校验均未改。
与上游的关系 / Upstream relationship
上游参考 / Upstream reference: N/A,针对本仓库 #756 的测试。
关联 Issue / Related issue
Related #756。不使用自动关闭关键字。
#757 是独立的 format1 → format2 迁移与部署阻断;本 PR 未解决、未验证该事项,也不授权任何生产操作。
变更类型 / Type of change
验证 / Verification
实际执行环境无法克隆完整仓库:
git clone --depth 1 https://github.com/TokenNotIncluded/api.lmm.best.git /mnt/data/api-lmm-756退出 128,错误为Could not resolve host: github.com。该退出码属于克隆命令,不是 go test 的退出码。本地未发现 PostgreSQL 工具及所需依赖缓存;现有 Replit 环境查询返回 paused,没有执行结果。没有使用 CI 替代本地测试。通过 GitHub 连接读取并核对原文件 blob SHA,在本地文件副本上完成修改和格式检查,再提交到独立分支。已读取提交差异,并确认远端三个文件的 blob SHA 与本地检查的文件相同。
实际执行:
另用本地脚本核对原测试名称保留、没有 t.Skip、路由断言未改、BI01 固定金额与后续结算断言未改。这些只是文件和格式检查,不是编译、运行或数据库验收。
go test -p 2 ./... -count=1go vet -p 2 ./...scripts/local-release-tests.py的候选版本记录未解决事项
保留 #756 开启及本 PR 的 Draft 状态。需要在全新本机隔离 PostgreSQL 集群和合成数据环境中,先验证基准版本,再针对候选提交实际运行完整测试;通过后执行 go vet,并通过
scripts/local-release-tests.py记录精确候选 revision、命令、退出码及日志哈希。已有 SQLite/miniredis fixture 应继续保持独立,不能连接生产数据库或复用生产环境变量。三项安全边界检查遵循
.github/SECURITY.md私下归因;公开 PR 不附这些用例的报文、凭据、敏感行为或原始日志。当前没有足够证据将它们认定为漏洞或过期测试。若确认漏洞,应进入私密 Security Advisory 流程。截图或日志 / Screenshots or logs
仅列出上面的非敏感格式检查结果。未上传原始应用日志、生产数据或安全复现内容。没有生成或伪造 local-release-tests 发布资格证据。
提交检查 / Checklist
未连接生产数据库,未创建生产账号,未部署,未触发或等待日常测试 CI / CodeQL,未发布版本。