Bump vllm from 0.6.3 to 0.26.0 in /verifiers/berkeley-function-call-leaderboard - #10
Conversation
Bumps [vllm](https://github.com/vllm-project/vllm) from 0.6.3 to 0.26.0. - [Release notes](https://github.com/vllm-project/vllm/releases) - [Changelog](https://github.com/vllm-project/vllm/blob/main/RELEASE.md) - [Commits](vllm-project/vllm@v0.6.3...v0.26.0) --- updated-dependencies: - dependency-name: vllm dependency-version: 0.26.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
EntelligenceAI PR SummaryUpdated the Berkeley Function-Call Leaderboard’s optional Review Scorecard
Issues found:
Fix before merge but low risk — the change is narrowly scoped and correctly targets the optional vLLM evaluation dependency, with no high-impact runtime surface touched. However, the Need to merge before these are addressed? Anyone with write access can comment Evaluated against
Files requiring special attention
|
WalkthroughUpgrades the optional OSS evaluation dependency on vLLM from version 0.6.3 to 0.26.0. No other dependencies or project configuration are changed. Changes
Sequence DiagramThis diagram shows the interactions between components: sequenceDiagram
title BFCL OSS Evaluation with Updated vLLM Dependency
actor Evaluator as "BFCL Evaluator"
participant Config as "Project Configuration\n(pyproject.toml)"
participant Resolver as "Python Dependency Resolver"
participant Runtime as "vLLM Runtime"
participant Model as "Language Model"
Evaluator->>Config: Select oss_eval_vllm optional dependency
Config->>Resolver: Resolve vLLM requirement
Note over Config, Resolver: Modified interaction:\nrequires vllm==0.26.0\n(replaces vllm==0.6.3)
Resolver-->>Evaluator: Install compatible vLLM package
Evaluator->>Runtime: Initialize evaluation backend
Runtime->>Model: Load model
Model-->>Runtime: Ready for inference
loop For each BFCL test case
Evaluator->>Runtime: Submit prompt and tool definitions
Runtime->>Model: Generate function-call response
Model-->>Runtime: Return model output
Runtime-->>Evaluator: Return generated function call
Evaluator->>Evaluator: Score response
end
Evaluator-->>Evaluator: Produce BFCL evaluation results
|
![entelligence-ai-pr-reviews[bot]](https://avatars.githubusercontent.com/in/932812?s=60&v=4){kind=small}
|
|
||
| [project.optional-dependencies] | ||
| oss_eval_vllm = ["vllm==0.6.3"] | ||
| oss_eval_vllm = ["vllm==0.26.0"] |
There was a problem hiding this comment.
Installing the documented .[oss_eval_vllm] extra now fails dependency resolution: this project pins openai==1.65.0, while vllm 0.26.0 requires openai>=2.0.0, so users cannot install the optional vLLM backend.
Prompt to fix with AI
Copy this prompt into your AI coding assistant to fix this issue.
In verifiers/berkeley-function-call-leaderboard/pyproject.toml:25 and 50, resolve the dependency conflict between the project's exact OpenAI pin and vllm 0.26.0's openai>=2.0.0 requirement. Choose compatible versions while preserving BFCL's OpenAI API compatibility, then verify `pip install -e '.[oss_eval_vllm]'` resolves successfully.
|
Superseded by #12. |
Bumps vllm from 0.6.3 to 0.26.0.
Release notes
Sourced from vllm's releases.
... (truncated)
Commits
568afb3[CI/Build] Refresh tags before building macOS wheel (#49901)f265493[ROCm] [Release] [Bugfix] Fix the per commit wheel release pipeline. (#49245)ffd46bf[Bugfix] Register axk1 config to fix A.X-K1 init (#49727)ffd6ee4[CI] Bump PyTorch Compilation Unit Tests timeout to 150 min (#49606)bb26ce8[CI] Increase timeout of pytorch-compilation-unit-tests (#49450)091db8b[CI] Increase timeouts for jobs exceeding current limits (#49374)ba694b8[CI] Bump timeout ofentrypoints-integration-api-server-openai-part-2(#49359)e5949f1[Bugfix] handle grammar compilation failures to avoid engine crash (#47312)8b30569[Bugfix] Fix DeepGEMM warmup when using `FlashInferFp8DeepGEMMDynamicBlockSca...9d37a50[Bugfix][Attention] Ignore empty MLA context chunks during merge (#49294)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.