fix(design): log per-harness auto-enqueue skips - #127
Conversation
Round-loop discarded EnqueueRoundResult.skipped, so quota/elimination failures had no operational signal. Warn each skip and document hex-hotkey miner lookups in external troubleshoot.
|
Warning Review limit reached
Next review available in: 6 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Summary
EnqueueRoundResult.skippedentry (harness id, hotkey, round, reason) instead of discarding them silently.GET /v1/miners/{hotkey}), latest-active harness, scheduled quota, and admin requeueskipped.reason.Context
Live check for miner harness
bed1f30c…/ hotkey587a2406…on round 206772: not a skip — run09880a61…is queued (enqueued ~05:22 UTC after #124 prod pin). Platform had 194/194 active harnesses with a run. Silent-skip logging was still a real ops gap for future quota/elimination cases; enqueue itself is healthy.Test plan
cargo test -p design-http --lib auto_enqueuecargo clippy -p design-challenge --all-targets -- -D warningsauto-enqueue skipped harnesswhen a harness hits scheduled quota (or via admin requeue dry observation)