-
Notifications
You must be signed in to change notification settings - Fork 43
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
Do a full type detection when creating cache #527
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,11 @@ | ||
------------------------------------------------------------------- | ||
Thu Jan 5 11:58:05 UTC 2017 - mfilka@suse.com | ||
|
||
- bnc#956755 | ||
- Use full type detection when caching network configuration to | ||
solve ambiguos configurations (like bridge over wlan). | ||
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. ambiguous But this is describing implementation details and tells the user nothing about the bug this is fixing or its symptoms. 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. This is an internal module which is used mainly by other yast parts. And the change is implementation detail bcs in perfect code internal sorting of NetworkInterfaces' cache would be really internal. Sadly we more or less expose it's organization, so any change in it is public as well. |
||
- 3.2.12 | ||
|
||
------------------------------------------------------------------- | ||
Thu Jan 5 11:35:23 UTC 2017 - mfilka@suse.com | ||
|
||
|
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.
When I want to understand the change, I look up the names in http://apitalism.herokuapp.com/?q=GetType
and get
http://www.rubydoc.info/github/yast/yast-yast2/Yast%2FNetworkInterfacesClass%3AGetTypeFromIfcfg
Detects device type according given ifcfg configuration
http://www.rubydoc.info/github/yast/yast-yast2/Yast%2FNetworkInterfacesClass%3AGetType
Detects device type according cached data
If cached ifcfg for given device is found it is used as parameter for GetTypeFromIfcfgOrName( dev, ifcfg). Otherwise is device handled as unconfigured and result is equal to GetTypeFromIfcfgOrName( dev, nil)
I am still lost. What is the difference in the return value for this particular bug?
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.
Difference is that
GetTypeFromIfcfgOrName
uses ifcfg file or name for device type detection. It is just a subset of whole type detection process which is implemented inGetType
.GetType
is the only function which should be present in public API (but it is not bcs of ycp). Particular example of collision is described in the commit message.