-
Notifications
You must be signed in to change notification settings - Fork 0
megaraid: Properly handle permanent Path and device Path #20
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
Merged
Merged
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
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 |
|---|---|---|
|
|
@@ -573,10 +573,12 @@ func getPaths(vdp *VDProperties, pdrives []*physicaldrive.PhysicalDrive) ( | |
|
|
||
| pd := pdrives[0] | ||
|
|
||
| permanentPath = computePermanentPath(pd) | ||
| if !CustomFileExists(permanentPath) { | ||
| return devicePath, "", errors.New("failed to get permanent path from physical drive") | ||
| err = pd.ComputePaths() | ||
| if err != nil { | ||
| return devicePath, "", errors.Wrap(err, "failed to compute paths from physical drive") | ||
| } | ||
|
|
||
| return pd.DevicePath, pd.PermanentPath, nil | ||
|
Comment on lines
+576
to
+581
Contributor
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. Cf com above, would make this part less implicity and enable more precise error handling |
||
| } | ||
|
|
||
| // If the devicePath is empty let's retrieve it from the permanent path | ||
|
|
||
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.
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.
WDYT about writing this as 2 methods (permanent and device) that returns the computed values instead of modifying implicitly ?
Better error handling, readability and testability IMO
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.
Since it's a method of physicalDrive struct to me it's cleaner to update in place
For separating permanent and device I could but one depends on the other and in all case we want to compute boths so... I don't know if it brings a lot of value proper error message are handled by this function and not the upper ones