Skip to content

Conversation

@shenoyvvarun
Copy link
Contributor

@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

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request cherry-picks two bug fixes: one for multimodal profiler token calculation and another for Llama 3.1 tool call parsing. The changes look correct and align with the goals. However, I've identified a critical security vulnerability and another high-severity issue in the new development Dockerfile. Additionally, there is an unresolved merge conflict in one of the Python files that needs to be addressed.

&& git config --global color.diff.new "green bold" \
&& git config --global color.diff.whitespace "red reverse" \
&& git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset - %s %Cgreen(%cr) %C(bold blue)<%an>%Creset%C(auto)%d%Creset' --abbrev-commit --" \
&& git config --global http.sslVerify false \

Choose a reason for hiding this comment

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

critical

Disabling SSL verification for git globally with http.sslVerify false is a significant security vulnerability. It exposes the container to Man-in-the-Middle (MITM) attacks during git operations, as it will trust any SSL certificate.

This setting should be removed. If there's a specific need to connect to a git repository with a self-signed certificate, it should be configured on a per-repository basis, not globally.

return self._get_mm_max_tokens(seq_len,
mm_counts,
mm_embeddings_only=False)
>>>>>>> 0e36abf99 ([Bugfix] Correct max tokens for non-contiguous embeds (#21798))

Choose a reason for hiding this comment

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

critical

This file contains an unresolved merge conflict marker. This must be resolved before the pull request can be merged.

RUN apt update -y \
&& apt install -y --no-install-recommends gnupg \
&& echo "deb http://developer.download.nvidia.com/devtools/repos/ubuntu2004/amd64 /" | tee /etc/apt/sources.list.d/nvidia-devtools.list \
&& apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub \

Choose a reason for hiding this comment

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

high

Fetching GPG keys over an unencrypted http connection is insecure and vulnerable to Man-in-the-Middle attacks. Please use https instead. Additionally, apt-key is deprecated and its use should be avoided in favor of storing keys in /usr/share/keyrings/.

    && apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub \

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants