Conversation
Co-authored-by: OpenAI Codex <noreply@openai.com> Signed-off-by: Alex <jihui.huang@daocloud.io>
Co-authored-by: OpenAI Codex <noreply@openai.com> Signed-off-by: Alex <jihui.huang@daocloud.io>
|
/ci run |
|
✅ @Alex-ai-future, CI is now available for this PR.
|
|
✅ Triggered Buildkite CI #87053 for commit |
|
/ci retry |
|
✅ Queued 3 failed job(s) for retry in Buildkite CI #87053. |
|
/ci retry |
|
✅ Queued 2 failed job(s) for retry in Buildkite CI #87053. |
|
/ci retry |
|
✅ Queued 2 failed job(s) for retry in Buildkite CI #87053. |
|
/ci retry |
|
✅ Triggered Buildkite CI #87175 for commit |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 SummarySummary by CodeRabbit
Walkthrough
ChangesLookup batch filtering
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Async KV lookup batching now skips entries removed during request cleanup or superseded by newer generations, avoiding unnecessary backend lookups without changing already queued or in-flight work. The supplied regression coverage supports merge readiness. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
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 |
|
/ci retry |
|
✅ Queued 1 failed job(s) for retry in Buildkite CI #87175. |
|
/ci retry |
|
✅ Triggered Buildkite CI #87204 for commit |
|
/ci run |
|
✅ Triggered Buildkite CI #87211 for commit |
|
/ci run |
|
✅ Triggered Buildkite CI #87230 for commit |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/ci run |
|
✅ Triggered Buildkite CI #87431 for commit |
…ct#55075) Signed-off-by: Alex <jihui.huang@daocloud.io> Co-authored-by: OpenAI Codex <noreply@openai.com> Co-authored-by: Or Ozeri <oro@il.ibm.com> Signed-off-by: Jyotirmoy Roy <jyotirmoyroy649@gmail.com>
Purpose
Skip a secondary-tier async lookup when its last requester finishes before
the scheduler flushes that step's lookup batch.
User case
Kto the current step's async lookup batch.on_schedule_end()callsflush().flush()still submittedKto the background worker.The fix revalidates each entry against the scheduler-owned lookup state before
queueing it. It drops only missing or superseded generations; a key shared by
another active request remains eligible. It deliberately does not attempt to
cancel batches that are already queued or backend calls already in flight.
No open PR was found for this flush-before-submit cancellation case. This is
complementary to #54872, which protects the result side after a batch has
already been submitted.
Test Plan
The regression test confirms that cleanup before
flush()results in nobatch_lookup()call. The focused suite retains coverage for shared entriesand stale results after submission.
Test Result
Model evaluation is not applicable; this is a scheduler lifecycle fix.
AI assistance was used for code and test development. The human submitter
reviewed every changed line and the test result.
Checklist