fix(polymarket): retry deferred uploader activation - #524
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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)
📝 WalkthroughWalkthroughDeferred market upload verification now retries transient ChangesDeferred upload retry behavior
Estimated code review effort: 3 (Moderate) | ~15–30 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@deployment/aliyun/test-polymarket-raw-ops-control-plane.sh`:
- Around line 4359-4366: Update the pid-delayed mock’s readlink handling in the
`--property=MainPID` and corresponding `4380-4387` branches so an exact
`/proc/0/exe` request returns a non-matching path before the generic readlink
response. Add or adjust the targeted test to verify PID 0 validation is rejected
while preserving existing delayed-PID behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 818e90f8-2e07-4dd2-a41a-6477a9184320
📒 Files selected for processing (2)
deployment/aliyun/polymarket-raw-ops-cutover.shdeployment/aliyun/test-polymarket-raw-ops-control-plane.sh
ea768fe to
1f47112
Compare
Change contract
Within the existing 10-second deferred market-uploader admission loop, retry
while a new active/activating systemd invocation has not yet exposed a positive
MainPIDor readable/proc/PID/exe. Preserve exact-binary, failed-unit, andtimeout fail-closed behavior.
Issue relationship
Refs #523
Out of scope
Collector/uploader data semantics, historical spool cleanup, Gate duration,
Python health cadence, research, snapshot/#235, evaluator/MCTS, CI
restructuring, and production mutation.
Dependency or merge order
None. This is based on exact main
8dc486906f1e2fcf4e940a6e9400c8433e61158cand is independently reversible.Focused validation
pid-delayedbefore the implementation.bash deployment/aliyun/test-polymarket-raw-ops-control-plane.sh.bash -non both changed scripts.git diff --check.10-second timeout remain fail-closed.
Rollout / rollback impact
After merge, build an exact-main artifact and repeat the real closed-segment
preflight. Reuse the already-passed 900-second Gate only if its immutable
candidate/source/control/bundle identities still match the new artifact;
otherwise run a fresh Gate. Production cutover remains governed by the existing
checksum-protected Python rollback snapshot and stop rules.
Why no PRD
This is a small, fully specified production activation race with a focused
failing proof; a PRD would add no product decision.