test(forks): assert the sync-default audit fan-out against real audit_log rows - #8418
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
All reported issues were addressed across 2 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
|
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
Summary
setForkSyncDefaultaudit fan-out is now asserted against realaudit_logrows infork-sync.integration.ts: one entry per changed lineage member, filed in that member's own workspace, under the stored workspace name, with the origin workspace in metadatarecordAuditmock calls (repo testing rules; flagged on v0.9.6: search improvements, forking fixes, tables correctness #8410).sync-default.test.tskeeps only the lineage-moved 409 guard, the one branch real Postgres can't stageworkspacetable, not the use case's ownRETURNING, so a wrong name can't agree with itselfType of Change
Testing
fork-sync.integration.ts(real Postgres): 13/13RETURNINGthat yields the id as the name each turn the integration test redsync-default.test.ts: 1/1bun run lint,type-check,check:audits(52/52),docs-manifest:checkChecklist
test-auditauthoring gate)