[Bugfix] Fix KeyError: 1 When Using LoRA adapters

[BlackBird-Coding]

FIX #5113
During batch inference, when using LoRA adapters, the process crashes due to attempting to remove a LoRA adapter that has already been removed.
To address this problem, I have added a condition to ensure that the LoRA adapter is only removed if it exists in the curr_loras list:

if (
    curr_loras is not None
    and seq_group.lora_int_id > 0
    and seq_group.lora_int_id in curr_loras
):
        curr_loras.remove(seq_group.lora_int_id)

By checking if seq_group.lora_int_id is present in curr_loras before attempting to remove it, we prevent the crash that occurs when trying to remove a LoRA adapter that has already been removed.

---

PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

• [Bugfix] for bug fixes.
• [CI/Build] for build or continuous integration improvements.
• [Doc] for documentation fixes and improvements.
• [Model] for adding a new model or improving an existing model. Model name should appear in the title.
• [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
• [Kernel] for changes affecting CUDA kernels or other compute kernels.
• [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
• [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
• [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

• We adhere to Google Python style guide and Google C++ style guide.
• Pass all linter checks. Please use format.sh to format your code.
• The code need to be well-documented to ensure future contributors can easily understand the code.
• Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
• Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

• After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
• After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
• After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
• Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

[Yard1]

Lgtm, thanks!

[flexorRegev]

@BlackBird-Coding are you planning to finish this PR with the failing stuff? or is it just flaky tests?

[Yard1]

It just needs lint to be fixed

[BlackBird-Coding]

It just needs lint to be fixed

I've been working on this code and have fixed all the lint errors, but I'm still seeing a failure in the 'AMD: Prefix Caching Test'. I'm not quite sure what the issue might be

[BlackBird-Coding]

[Yard1]

@BlackBird-Coding some of the CI errors are unrelated to this PR (the CI is flaky), but we definitely need lint check to pass.

[BlackBird-Coding]

@Yard1 Thanks for the heads up about the failing lint check. I've resolved the linting issues and all checks are passing now, except for some unrelated CI flakiness as you mentioned.

[Yard1]

@BlackBird-Coding can you merge master into your branch, that should fix the speculative decoding CI

[BlackBird-Coding]

@Yard1 Now all check have passed, I truly appreciate your expertise and willingness to help.