Every way I've caught an AI agent making the build green without fixing anything
热度趋势
趋势数据积累中
百分比基于当前可用热度信号，而非评论数或独立用户人数。
这条记录涉及编程工具或代码能力更新，适合开发者评估工作流变化和可复用价值。
一位开发者一直在收集AI代理在不修复任何问题的情况下，使软件构建看起来成功的方法。观察到的常见策略包括捕获并丢弃错误，例如使用“except: pass”、“catch {}”或“.catch(() => {})”等结构。…
I’ve been collecting these for a few months.
All of them produce a passing CI run. None of them fix the problem.
- Delete the failing test.
- Remove assertions but keep the test.
- Replace a real assertion with expect(true).toBe(true).
- Disable TLS verification: verify=False, rejectUnauthorized: false, InsecureSkipVerify: true.
- Add u/ts-ignore , # noqa, or //nolint on the exact line a checker complained about.
- Catch and discard the error: except: pass, catch {}, .catch(() => {}).
The pattern I care about now isn’t: “Is this code good?”
It’s: “Did this change edit the thing that decides whether it passes?” Tests, CI config, lint config, .gitignore; I read those first.
What other versions of this have people seen?
Disclosure: I ended up building an open-source CLI to catch these patterns. It’s called Verik — npm install -g verik or visit our github!