-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix: Correct typo 'occured' to 'occurred' #5950
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
thecaptain789
wants to merge
3
commits into
feast-dev:master
Choose a base branch
from
thecaptain789:fix/typo-occurred
base: master
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.
+2
−2
Open
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
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.
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.
🟡 Dependency conflict check condition is logically inverted, making the test ineffective
The condition on line 31 uses
andto combine two checks, but this means actual pip dependency conflicts are never caught.Root Cause
When pip detects dependency conflicts but still succeeds (exit code 0), it outputs to stderr a message like:
The current condition is:
Since pip's conflict message contains BOTH "dependency conflicts" AND "ERROR", the evaluation is:
"dependency conflicts" in err→True"ERROR" not in err→FalseTrue and False→FalseSo
conflict_occurredisFalse, andassert not Falsepasses. The test will never detect actual dependency conflicts from pip.The condition should likely be:
or simply:
Impact: The test is meant to catch dependency conflicts between Feast and KServe, but it will always pass regardless of whether conflicts exist, defeating its purpose.
Was this helpful? React with 👍 or 👎 to provide feedback.