|
|
Chromium Code Reviews|
Created:
3 years, 8 months ago by Evan Stade Modified:
3 years, 8 months ago Reviewers:
stevenjb CC:
chromium-reviews, kalyank, stevenjb+watch_chromium.org, sadrul, oshima+watch_chromium.org Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionChromeOS - Fix some network related strings.
This fixes the ethernet string and removes broken/unused code for VPN
address in network info bubble.
BUG=706085
Review-Url: https://codereview.chromium.org/2781233002
Cr-Commit-Position: refs/heads/master@{#460841}
Committed: https://chromium.googlesource.com/chromium/src/+/4980bf9a7b63805fceae1fa3fb17922abb99f59a
Patch Set 1 #
Total comments: 2
Patch Set 2 : no vpn #
Messages
Total messages: 17 (9 generated)
Description was changed from ========== ChromeOS - Fix some network related strings. BUG=706085 ========== to ========== ChromeOS - Fix some network related strings. This fixes the ethernet string and a related bug for VPN networks. BUG=706085 ==========
estade@chromium.org changed reviewers: + stevenjb@chromium.org
https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... File ash/common/system/chromeos/network/network_state_list_detailed_view.cc (right): https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... ash/common/system/chromeos/network/network_state_list_detailed_view.cc:425: handler->FormattedHardwareAddressForType(NetworkTypePattern::VPN()); as far as I can tell this always returns null. Steven, you added this (VPN address line) in [1]. Is it possible for a VPN service to have an address? If so, perhaps it is an oversight that FakeShillManagerClient doesn't set an address. If not, we can delete this code and the VPN_ADDRESS string. [1] https://codereview.chromium.org/12387065
https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... File ash/common/system/chromeos/network/network_state_list_detailed_view.cc (right): https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... ash/common/system/chromeos/network/network_state_list_detailed_view.cc:425: handler->FormattedHardwareAddressForType(NetworkTypePattern::VPN()); On 2017/03/30 02:42:50, Evan Stade wrote: > as far as I can tell this always returns null. Steven, you added this (VPN > address line) in [1]. Is it possible for a VPN service to have an address? If > so, perhaps it is an oversight that FakeShillManagerClient doesn't set an > address. If not, we can delete this code and the VPN_ADDRESS string. > > [1] https://codereview.chromium.org/12387065 Don't rely on the fake implementations for 100% correct Shill behavior, that would be a monumental effort :) We add support as we need it for testing. That said, a VPN should have an IP address (network->ip_address()), but not a hardware (MAC) address (there is no associated device). I don't recall the history of this code. It's possible it has simply always been wrong and nobody noticed.
On 2017/03/30 17:10:05, stevenjb wrote: > https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... > File ash/common/system/chromeos/network/network_state_list_detailed_view.cc > (right): > > https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... > ash/common/system/chromeos/network/network_state_list_detailed_view.cc:425: > handler->FormattedHardwareAddressForType(NetworkTypePattern::VPN()); > On 2017/03/30 02:42:50, Evan Stade wrote: > > as far as I can tell this always returns null. Steven, you added this (VPN > > address line) in [1]. Is it possible for a VPN service to have an address? If > > so, perhaps it is an oversight that FakeShillManagerClient doesn't set an > > address. If not, we can delete this code and the VPN_ADDRESS string. > > > > [1] https://codereview.chromium.org/12387065 > > Don't rely on the fake implementations for 100% correct Shill behavior, that > would be a monumental effort :) We add support as we need it for testing. > > That said, a VPN should have an IP address (network->ip_address()), but not a > hardware (MAC) address (there is no associated device). I don't recall the > history of this code. It's possible it has simply always been wrong and nobody > noticed. Are you suggesting we should show the ip address then?
On 2017/03/30 17:26:25, Evan Stade wrote: > On 2017/03/30 17:10:05, stevenjb wrote: > > > https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... > > File ash/common/system/chromeos/network/network_state_list_detailed_view.cc > > (right): > > > > > https://codereview.chromium.org/2781233002/diff/1/ash/common/system/chromeos/... > > ash/common/system/chromeos/network/network_state_list_detailed_view.cc:425: > > handler->FormattedHardwareAddressForType(NetworkTypePattern::VPN()); > > On 2017/03/30 02:42:50, Evan Stade wrote: > > > as far as I can tell this always returns null. Steven, you added this (VPN > > > address line) in [1]. Is it possible for a VPN service to have an address? > If > > > so, perhaps it is an oversight that FakeShillManagerClient doesn't set an > > > address. If not, we can delete this code and the VPN_ADDRESS string. > > > > > > [1] https://codereview.chromium.org/12387065 > > > > Don't rely on the fake implementations for 100% correct Shill behavior, that > > would be a monumental effort :) We add support as we need it for testing. > > > > That said, a VPN should have an IP address (network->ip_address()), but not a > > hardware (MAC) address (there is no associated device). I don't recall the > > history of this code. It's possible it has simply always been wrong and nobody > > noticed. > > Are you suggesting we should show the ip address then? Yeah, we should show just the IP address for VPN, but the logic is actually broken. I'm going to put up a quick fix for that, but here you can just remove vpn_address entirely.
Description was changed from ========== ChromeOS - Fix some network related strings. This fixes the ethernet string and a related bug for VPN networks. BUG=706085 ========== to ========== ChromeOS - Fix some network related strings. This fixes the ethernet string and removes broken/unused code for VPN address in network info bubble. BUG=706085 ==========
updated, ptal
The CQ bit was checked by estade@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by estade@chromium.org
The CQ bit was checked by estade@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 20001, "attempt_start_ts": 1490899229010770,
"parent_rev": "4178c1385df3da6a8ba8dc1a0adb06f628a9ebdc", "commit_rev":
"4980bf9a7b63805fceae1fa3fb17922abb99f59a"}
Message was sent while issue was closed.
Description was changed from ========== ChromeOS - Fix some network related strings. This fixes the ethernet string and removes broken/unused code for VPN address in network info bubble. BUG=706085 ========== to ========== ChromeOS - Fix some network related strings. This fixes the ethernet string and removes broken/unused code for VPN address in network info bubble. BUG=706085 Review-Url: https://codereview.chromium.org/2781233002 Cr-Commit-Position: refs/heads/master@{#460841} Committed: https://chromium.googlesource.com/chromium/src/+/4980bf9a7b63805fceae1fa3fb17... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/chromium/src/+/4980bf9a7b63805fceae1fa3fb17... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
