-
Notifications
You must be signed in to change notification settings - Fork 102
Add bc decorator #6949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
zhewenl
wants to merge
3
commits into
pytorch:main
Choose a base branch
from
zhewenl:add-annotation-support-for-bc-linter
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add bc decorator #6949
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
"""Utilities for marking API compatibility checks.""" | ||
|
||
from __future__ import annotations | ||
|
||
from typing import Callable, TypeVar, Any | ||
|
||
F = TypeVar("F", bound=Callable[..., Any]) | ||
|
||
|
||
def check_compat(*, enable: bool = True) -> Callable[[F], F]: | ||
"""Decorator used by stronghold to toggle API compatibility checks. | ||
|
||
When ``enable`` is ``False`` the decorated function will be skipped by the | ||
backward compatibility linter. | ||
""" | ||
|
||
def decorator(func: F) -> F: | ||
# Not used in the linter, but useful for debugging. | ||
setattr(func, "_bc_linter_enable", enable) | ||
return func | ||
|
||
return decorator | ||
|
||
# Alias decorator to unconditionally disable the backward compatibility linter. | ||
skip: Callable[[F], F] = check_compat(enable=False) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# BC Linter for vLLM | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. discussed with @izaitsevfb offline, we will try to make bc decorator more generalized by:
|
||
PR: https://github.com/vllm-project/vllm/pull/21234 | ||
|
||
## Code Path | ||
Cover the following code path: | ||
- vllm/v1/attetion/** | ||
- vllm/v1/core/** | ||
|
||
Additionally, we should have flexibility to cover other code path in the future. | ||
|
||
## Lint Rules | ||
- Check backward compatibility for dataclasses/functions defined python files in code path above | ||
- The default behavior for linter is to check all the dataclasses/public functions in the code path, but we provide an option to skip bc-linter for some experimental dataclasses/functions with `@bc_linter_skip` decorator |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the current decorator behavior is "opt-out" — the default behavior (public function is checked) is changed only when:
Is this the intended behavior? If yes, can't we just simplify the opt-out syntax to something like
@bc_linter.skip
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I was checking https://github.com/search?q=repo%3Apytorch%2Fpytorch%20torch.fx._compatibility.compatibility&type=code, but adding skip is a very good idea!