chore: Update CODEOWNERS, adding PeaBrane to some examples subdirs

[PeaBrane]

Overview:

Summary by CodeRabbit

• Chores
  • Updated code ownership for specific example directories.

[coderabbitai]

Walkthrough

The CODEOWNERS file has been updated to add the user @PeaBrane as a code owner for the /examples/llm/, /examples/vllm_v0/, and /examples/vllm_v1/ directories. No other directories or ownership rules were changed.

Changes

File(s)	Change Summary
CODEOWNERS	Added @PeaBrane as a code owner for three example directories.

Possibly related PRs

• chore: Add Richard Huo to CODEOWNERS, and add TRTLLM section #1311: Also modifies CODEOWNERS to add new code owners for example directories, focusing on ownership granularity.
• chore: add rudy as codeowner #1257: Adds @PeaBrane as a code owner, but for different directory scopes and file types.
• chore: Update CODEOWNERS #1380: Restructures CODEOWNERS for /examples/, including granular entries for the same subdirectories.

Poem

A rabbit hopped with nimble feet,
To CODEOWNERS, a task to complete.
With a twitch of nose and a flick of ear,
@PeaBrane now helps keep things clear.
In the garden of code, with owners anew,
The examples grow strong, thanks to this crew! 🥕

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CODEOWNERS (1)

23-23: Consider alphabetizing owner lists for easier maintenance

The newly-added @PeaBrane entry is correct, but the owner lists for /examples/llm/, /examples/vllm_v0/, and /examples/vllm_v1/ are now a mix of alphabetical and ad-hoc ordering. Keeping owners alphabetized (or adopting another deterministic order) makes future edits and merge-conflict resolution easier.

No functional impact—purely a readability/maintenance nit.

Also applies to: 27-28

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3f15ee and 4eb347b.

📒 Files selected for processing (1)

• CODEOWNERS (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: PeaBrane
PR: ai-dynamo/dynamo#1285
File: lib/llm/src/kv_router/scheduler.rs:260-266
Timestamp: 2025-05-30T06:34:12.785Z
Learning: In the KV router scheduler code, PeaBrane prefers fail-fast behavior over silent failure handling. When accessing worker metrics data that could be out-of-bounds (like dp_rank indexing), explicit panics are preferred over graceful degradation with continue statements to ensure data integrity issues are caught early.

CODEOWNERS (1)

Learnt from: PeaBrane
PR: ai-dynamo/dynamo#1409
File: examples/router_standalone/worker.py:171-186
Timestamp: 2025-06-08T08:30:45.126Z
Learning: Example code in the `examples/` directory may intentionally use hard-coded values or simplified implementations that wouldn't be appropriate for production code, but are acceptable for demonstration and testing purposes.

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build and Test - vllm