Skip to content

Conversation

@wseaton
Copy link
Contributor

@wseaton wseaton commented May 15, 2025

Add a better error message if a user is likely running into the k8s service discovery issue: https://docs.vllm.ai/en/stable/serving/env_vars.html#environment-variables

I lost 20 minutes on this due to the default int() -> ValueError message , I think a better one would help.

@github-actions
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Member

@njhill njhill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @wseaton!

I feel like we should change the name of the env var used for the internal port if possible!

@njhill njhill added the ready ONLY add when PR is ready to merge/full CI is needed label May 15, 2025
@vllm-bot vllm-bot merged commit 6b31c84 into vllm-project:main May 16, 2025
66 of 68 checks passed
zzzyq pushed a commit to zzzyq/vllm that referenced this pull request May 24, 2025
rabi added a commit to rabi/vllm that referenced this pull request May 26, 2025
The urllib.parse.urlparse() function itself does not raise
an exception during the parsing of a URL. However, certain
attributes of the returned ParseResult object (e.g., .port)
may raise a ValueError when accessed if they contain invalid
values.

Issue introduced in vllm-project#18209

FIX: vllm-project#18617
Signed-off-by: rabi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready ONLY add when PR is ready to merge/full CI is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants