This is an automated email from the ASF dual-hosted git repository.
vterentev pushed a change to branch fix-vllm-10-08
in repository https://gitbox.apache.org/repos/asf/beam.git
discard 959e27e2de9 Add nvidia
discard 5f19342f450 Use latest sdk
discard cdf6fe035cb Fix triton version
discard ed3c03b8d8c Use old pypi dependencies
discard 1bb3f3048f3 Use float16 dtype and torch
discard b2751ef41d7 Use float32 dtype
discard 8d4f6e3423b Use float16 dtype
discard 0c5d8bf9ee6 Use float16 dtype, attention backend torch
discard 7fc6d7d1974 Fix kv-cache-dtype
discard 11251677715 Fix self method
discard 83ba4ff52a9 Fix dtypes
discard b551d04171e Fix vLLM Gemma, add vLLM extra, fix getting throughput
add d4760f95e49 Fix vLLM Gemma, add vLLM extra, fix getting throughput
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (959e27e2de9)
\
N -- N -- N refs/heads/fix-vllm-10-08 (d4760f95e49)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
