Followup task for LEADS-246 - Renaming api cache to agent#241
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
WalkthroughRenames DEFAULT_API_CACHE_SUBDIR to DEFAULT_AGENT_CACHE_SUBDIR and updates constants, SystemConfig global cache wiring, unit tests, documentation, and embedding config references to use the new ChangesCache Subdirectory Rename from API to Agent
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 `@config/system.yaml`:
- Line 9: The inline comment for the cache_base_dir setting is inaccurate: it
refers to "/agents" but the runtime uses ".caches/agent" (singular). Update the
comment next to the cache_base_dir YAML key to reflect the implemented subpaths
(e.g., ".caches/llm and .caches/agent") so the comment matches the actual
runtime directories used by the code that reads cache_base_dir.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f2b707ab-8169-4fbb-a73d-86077ec46a29
📒 Files selected for processing (4)
config/system.yamlsrc/lightspeed_evaluation/core/constants.pysrc/lightspeed_evaluation/core/models/system.pytests/unit/core/models/test_system.py
e4fc103 to
305d811
Compare
305d811 to
fa0e879
Compare
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/lightspeed_evaluation/core/models/system.py (1)
359-376:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winInclude embedding.cache_dir in deprecation warning check.
The deprecation warning logic checks
api.cache_dir(line 359) andllm_pool.defaults.cache_dir(line 363) but only checksembedding.cache_enabledat line 360. Now thatEmbeddingConfig.cache_diris being added inllm.py, this check should also verifyself.embedding.cache_dirfor consistency.🔧 Suggested fix
- has_embedding_cache_config = self.embedding.cache_enabled is False + has_embedding_cache_config = ( + self.embedding.cache_enabled is False or self.embedding.cache_dir + )🤖 Prompt for 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. In `@src/lightspeed_evaluation/core/models/system.py` around lines 359 - 376, The deprecation-check misses embedding.cache_dir: update the embedding check (variable has_embedding_cache_config) to mirror the others by considering either self.embedding.cache_enabled is False or self.embedding.cache_dir is set; i.e., change the condition that currently only tests embedding.cache_enabled to also check self.embedding.cache_dir so the deprecation warning triggers when an embedding cache directory is provided (refer to self.embedding.cache_enabled and self.embedding.cache_dir in your change).
🤖 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.
Outside diff comments:
In `@src/lightspeed_evaluation/core/models/system.py`:
- Around line 359-376: The deprecation-check misses embedding.cache_dir: update
the embedding check (variable has_embedding_cache_config) to mirror the others
by considering either self.embedding.cache_enabled is False or
self.embedding.cache_dir is set; i.e., change the condition that currently only
tests embedding.cache_enabled to also check self.embedding.cache_dir so the
deprecation warning triggers when an embedding cache directory is provided
(refer to self.embedding.cache_enabled and self.embedding.cache_dir in your
change).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f4eba70e-1a4f-45ae-96f4-a7573d4c4fd1
📒 Files selected for processing (8)
config/system.yamldocs/configuration.mdsrc/lightspeed_evaluation/core/constants.pysrc/lightspeed_evaluation/core/models/llm.pysrc/lightspeed_evaluation/core/models/system.pytests/integration/system-config-query.yamltests/integration/system-config-streaming.yamltests/unit/core/models/test_system.py
✅ Files skipped from review due to trivial changes (3)
- tests/integration/system-config-streaming.yaml
- tests/integration/system-config-query.yaml
- config/system.yaml
fa0e879 to
b4195d9
Compare
Description
Type of change
Tools used to create PR
Identify any AI code assistants used in this PR (for transparency and review context)
Related Tickets & Documents
Checklist before requesting a review
Testing
Summary by CodeRabbit