chore: bumps vllm to v0.24.0#1026
Conversation
|
👋 Hi! Thank you for contributing. We also recommend installing prek and configuring it to check your code before every local commit. |
| # initializing. Importing vllm.tokenizers.registry here would cause a circular | ||
| # import, so the call is deferred to SpyrePlatform.check_and_update_config. | ||
| # Workers use model execution paths, not the tokenizer registry, so they do | ||
| # not need this patch applied at module-level. |
There was a problem hiding this comment.
@gkumbhat this entire comment block should be moved to check_and_update_config then
Also- I'm really dubious about this working since the previous comment explains that this had to be here in order to be picked up by the spawned worker processes. If those don't run check_and_update_config because the config is simply serialized and sent to them, then the patch won't apply
Defers tokenizer registry patch from module-level to check_and_update_config to fix a circular import introduced in vLLM 0.24.0, where torch_utils.py now imports is_pin_memory_available at module-level (triggering platform resolution before torch_utils finishes initializing). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
|
bot:test |
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
|
bot:test |
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Both are now available unconditionally in vLLM 0.24.0 (the new minimum). Also updates vLLM:lowest CI entry to v0.24.0 and drops all pre-0.24.0 intermediate matrix entries. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com>
Defers tokenizer registry patch from module-level to check_and_update_config to fix a circular import introduced in vLLM 0.24.0, where torch_utils.py now imports is_pin_memory_available at module-level (triggering platform resolution before torch_utils finishes initializing). <!-- markdownlint-disable --> Enable `0.24.0` vLLM 1. vLLM upstream PR vllm-project/vllm#42656 seems to have slightly changed how blocks gets prepended, which seems to fail the tests. 2. vLLM upstream PR vllm-project/vllm#40299 seems to have fixed the mistral model file parsing issue, thus with move to `0.24.0` we can remove the patch we added for that entirely. <!-- Link related issues, e.g., `Fixes #` or `Relates to #456` --> <!-- Describe how you tested your changes. Include commands or steps to reproduce. --> - [ ] I have read the [contributing guidelines](https://docs.vllm.ai/projects/spyre/en/latest/contributing) - [ ] My code follows the project's code style (run `bash format.sh`) - [ ] I have added tests for my changes (if applicable) - [ ] I have updated the documentation (if applicable) - [ ] My commits include a `Signed-off-by:` line (DCO compliance) --------- Signed-off-by: gkumbhat <kumbhat.gaurav@gmail.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Defers tokenizer registry patch from module-level to check_and_update_config to fix a circular import introduced in vLLM 0.24.0, where torch_utils.py now imports is_pin_memory_available at module-level (triggering platform resolution before torch_utils finishes initializing).
Description
Enable
0.24.0vLLM0.24.0we can remove the patch we added for that entirely.Related Issues
Test Plan
Checklist
bash format.sh)Signed-off-by:line (DCO compliance)