(MOT-4235) fix(harness): use row-changed trigger name - #618
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe reactive automation e2e harness, prompt, evidence query, and README now consistently reference ChangesReactive automation trigger updates
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
skill-check — worker0 verified, 49 skipped (no docs/).
Four for four. Nicely done. |
Summary
database::row-changedRoot cause
The database worker changed its trigger type from
database::row-changetodatabase::row-changedin #614, but the separate Harness E2E suite retained the old name. Its shared startup check waited 60 seconds for a trigger that would never register, so every scenario failed before execution.Validation
cargo test -p harness-e2e— 41 passedcargo fmt --all -- --checkbash -n harness/tests/e2e/run-ci.shgit diff --checkRefs MOT-4235
Summary by CodeRabbit
Bug Fixes
Documentation
Tests