-
Notifications
You must be signed in to change notification settings - Fork 158
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
chore(feature-tracker): simplifies struct handling #1092
Merged
openshift-merge-bot
merged 4 commits into
opendatahub-io:incubation
from
bartoszmajsak:failsafe-ft-cleanup
Jul 3, 2024
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0e155eb
chore(feature-tracker): simplifies struct handling
bartoszmajsak 310e9d9
Merge branch 'incubation' into failsafe-ft-cleanup
bartoszmajsak 85c9f4d
Merge branch 'incubation' into failsafe-ft-cleanup
bartoszmajsak 1989530
fix: merge conflict
bartoszmajsak 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 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 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.
is there any possibility that after
associatedTracker = tracker
associatedTracker is nil?otherwise why not just
return client.IgnoreNotFound(f.Client.Delete(ctx, tracker))
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.
In theory, it can be not found in L62, and so it is
nil
. We do not propagate error on 404 (client.IgnoreNotFound(errGet)
), but we handle this case by simply skipping the Delete operation. CallingDelete
onnil
will panic.As to part if this can happen at runtime - under the hood it boils down to which operations are performed directly against
kube-apiserver
and which are taken from the local cache. I think it can be stale and might lead to such situation, so I thought it's better to handle it explicitly.