-
Notifications
You must be signed in to change notification settings - Fork 137
[SREP-4895] Fallback to deleted_cluster endpoint to get cluster information. #898
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
bergmannf
wants to merge
1
commit into
openshift:master
Choose a base branch
from
bergmannf:SREP-4895-fallback-to-deleted-cluster
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.
Open
Changes from all commits
Commits
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
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.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/osdctl
Length of output: 383
🏁 Script executed:
Repository: openshift/osdctl
Length of output: 820
🏁 Script executed:
Repository: openshift/osdctl
Length of output: 453
Fix non-idiomatic error message capitalization and use proper error wrapping in fmt.Errorf calls.
Multiple fmt.Errorf calls in this file violate ST1005. Line 153 should use
%winstead of%vfor error wrapping, and both lines 153 and 166 use capitalized error messages that should be lowercase. Similar issues appear at lines 83 and 130.Proposed fix
Also applies to: 83, 130 (same pattern: "Can't retrieve..." with
%vinstead of%w)🧰 Tools
🪛 golangci-lint (2.12.2)
[error] 153-153: ST1005: error strings should not be capitalized
(staticcheck)
🤖 Prompt for AI Agents
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.
Same capitalization is used as in all other messages - maintaining consistency is probably more useful than fixing just this one occurrence.
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.
@bergmannf, that's a fair point — fixing only the newly added line while leaving the same pattern at lines 83 and 130 unchanged would indeed create inconsistency.Would you like me to open a follow-up issue to track a style cleanup across the whole file (lowercasing error strings and switching
%vto%wwhere appropriate), so it can be addressed holistically in a dedicated PR?