main entrypoint: set env vars like vllm does

[dtrifiro]

cli_env_setup is responsible for setting VLLM_WORKER_MULTIPROC_METHOD='spawn' if the user hasn't overridden it through environment variables.

See https://github.com/vllm-project/vllm/blob/v0.10.0/vllm/entrypoints/utils.py#L151

Summary by CodeRabbit

• Chores
  • Improved environment setup during application startup for smoother initialization.

[coderabbitai]

Walkthrough

A call to cli_env_setup() from vllm.entrypoints.utils is added at the start of the __main__ block in src/vllm_tgis_adapter/__main__.py, ensuring environment setup occurs before any argument parsing or initialization. No other logic or control flow is changed.

Changes

Cohort / File(s)	Change Summary
Main entrypoint environment setup src/vllm_tgis_adapter/__main__.py	Added import and invocation of cli_env_setup() at the beginning of the main block. No other logic modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop, a skip, a setup call—
Now the main block stands so tall!
Before we parse, before we run,
The environment’s set—now isn't that fun?
With every change, we leap ahead,
A happy rabbit, well-prepared! 🐇✨

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 516f857 and ac059dd.

📒 Files selected for processing (1)

• src/vllm_tgis_adapter/__main__.py (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: tests (ubuntu-latest, 3.12, git+https://github.com/vllm-project/[email protected])
• GitHub Check: tests (ubuntu-latest, 3.12, git+https://github.com/vllm-project/vllm@main)

🔇 Additional comments (2)

src/vllm_tgis_adapter/__main__.py (2)

109-111: Good placement and behavior parity with vLLM.

Importing and calling cli_env_setup() at the very start of __main__ ensures the env var is set before parsing and engine init. This mirrors vLLM's intent. LGTM.

---

109-111: No fallback required for cli_env_setup
The project already declares vllm>=0.10.0 in pyproject.toml, so vllm.entrypoints.utils.cli_env_setup is guaranteed to exist. You can keep the import and call as-is:

• File: src/vllm_tgis_adapter/main.py
• Lines: 109–111

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch cli-env-vars

---

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.
• 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.

Support

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

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 docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[andy-neuma]

thanks!