Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(907)

Issue 81720043: Fix lp 1298703

Can't Edit
Can't Publish+Mail
Start Review
Created:
10 years, 1 month ago by dave
Modified:
10 years, 1 month ago
Reviewers:
mp+213195, axw
Visibility:
Public.

Description

Fix lp 1298703 One failure was a simple list ordering bug. The other two more complicated. NewAddress always returns an address with the scope of NetworkUnknown. In that case the results from calling unit.Public/PrivateAddress were essentially random. It feels like there are some other footguns in this area. Should NewAddress/NewAddresses create NetworkUnknown Address values ? What happens if they leak into the state and back to the client? How many other places are these things leaking into. I'd like to explore removing NewAddress/NewAddresses in a followup, if they are used only for testing (axw), then they are doing us a disservice. Thanks to Ian and Andrew for their assistance https://code.launchpad.net/~dave-cheney/juju-core/104-fix-lp-1298703/+merge/213195 (do not edit description out of merge proposal)

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+17 lines, -9 lines) Patch
A [revision details] View 1 chunk +2 lines, -0 lines 0 comments Download
M state/machine_test.go View 1 chunk +1 line, -1 line 0 comments Download
M state/unit_test.go View 2 chunks +14 lines, -8 lines 0 comments Download

Messages

Total messages: 2
dave_cheney.net
Please take a look.
10 years, 1 month ago (2014-03-28 04:42:14 UTC) #1
axw
10 years, 1 month ago (2014-03-28 04:50:25 UTC) #2
On 2014/03/28 04:42:14, dfc wrote:
> Please take a look.

LGTM

+1 to moving NewAddress(es)

There is one non-test place where NewAddress is used, and in that case it
legitimately does not know the address's scope. It would be good to make that
explicit anyhow.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b