⚡ Bolt: optimize triage cache eviction using islice

[sheepdestroyer]

💡 What: Optimize O(N) memory overhead during cache eviction by replacing list(triage_cache.keys())[:excess] with list(itertools.islice(triage_cache.keys(), excess)). Also fixes an ambiguous variable lint warning (E741) and drops an unused global import while keeping the essential local import.
🎯 Why: Python 3.7+ dictionaries maintain insertion order, so we can pop off the front for LRU/TTL caches without touching timestamps. Materializing the entire keys list via list() before slicing takes O(N) memory. Using itertools.islice avoids creating the full list, achieving O(1) memory overhead.
📊 Impact: Reduces memory spikes and garbage collection pressure when evicting entries from large caches.
🔬 Measurement: Profile memory usage during high eviction rates in the triage cache.

---

PR created automatically by Jules for task 18323913115939812235 started by @sheepdestroyer

Summary by Sourcery

Optimize triage cache cleanup to reduce memory usage during high-volume eviction.

Enhancements:

• Reduce triage cache eviction memory overhead by iterating only over the entries that need removal.
• Improve code clarity and lint compliance while removing an unused dependency import.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Optimizes triage-cache eviction by using itertools.islice to avoid O(N) temporary key-list allocation while preserving insertion-order eviction, and includes related lint and unused-import cleanup in router/main.py.

Flow diagram for memory-efficient triage cache eviction

flowchart TD
A["cleanup_triage_cache(max_size)"] --> B{"excess > 0"}
B -->|No| C["Keep cache unchanged"]
B -->|Yes| D["itertools.islice(triage_cache.keys(), excess)"]
D --> E["Pop oldest insertion-ordered keys"]
E --> F["triage_cache.pop(k, None)"]

Loading

File-Level Changes

Change	Details	Files
Reduce triage-cache eviction memory overhead by lazily selecting the oldest entries before removal.	Replace full key-list materialization and slicing with itertools.islice over dictionary keys. Continue evicting entries from the insertion-order front of the cache, preserving existing behavior.	router/main.py
Clean up lint and import issues in the main router module.	Rename the ambiguous token-counting variable to word_len. Remove unused Pydantic and typing imports. Remove the redundant local json import while retaining the module-level dependency.	router/main.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9e510b39-88e1-4628-84b9-e2a4d10b3771

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}