Expose RunLog seed failure stages - #1200
Conversation
|
No actionable comments were generated in the recent review. π βΉοΈ Recent review infoβοΈ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: π Files selected for processing (4)
π WalkthroughWalkthroughThe legacy seed flow now classifies per-user failures by inventory surface and phase. Results expose nullable failure metadata. Processing isolates failed users, avoids raw error logging, and documents the fields in the MCP capability schema. ChangesLegacy seed diagnostics
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant AdminRunLog
participant processUser
participant runSurfaceStep
participant TrackingRPC
AdminRunLog->>processUser: process one user
processUser->>runSurfaceStep: run workflow, job, or activation step
runSurfaceStep->>TrackingRPC: read, seed, or verify inventory
TrackingRPC-->>runSurfaceStep: success or error
runSurfaceStep-->>processUser: classified result
processUser-->>AdminRunLog: user result with failureStage and failurePhase
Possibly related PRs
π₯ Pre-merge checks | β 4 | β 1β Failed checks (1 warning)
β Passed checks (4 passed)
β¨ Finishing Touches π‘ 1π 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 |
|
π Preview deployed: https://kody-pr-1200.kody-a99.workers.dev Worker: Mocks:
|
Intent
Diagnose the one remaining production RunLog seed failure without exposing user-authored data.
Summary
failureStageandfailurePhasefields to admin seed resultsTesting
System changes
No seeding semantics change; operator diagnostics only.
Conductor report
STATUS: in-progress
What shipped: content-free seed failure staging is pushed; CI/merge/deploy and production rerun pending.
Risk self-assessment: low β additive admin output fields and safer logs.
Merged/deployed: no / no.
Scope spill: none.
Summary by CodeRabbit