https://codereview.appspot.com/7385049/diff/7001/worker/uniter/modes.go#newcode145
worker/uniter/modes.go:145: // handle the relations for the new unit
On 2013/02/25 10:31:57, fwereade wrote:
> Now the upgrade is complete, we'll need to check all relations again:
some might
> previously have been skipped (if they involved endpoints only
implemented in the
> new charm).
https://codereview.appspot.com/7385049/diff/7001/worker/uniter/uniter.go#newcode383
worker/uniter/uniter.go:383: // possibly even panic?
On 2013/02/25 10:31:57, fwereade wrote:
> Nope, this is just a straight-up error, I think. We don't have any way
of
> resolving it, or reporting it, it's true; but panicking won't improve
matters
> so... ;).
Done.
https://codereview.appspot.com/7385049/diff/7001/worker/uniter/uniter.go#newcode383
worker/uniter/uniter.go:383: // possibly even panic?
On 2013/02/25 10:31:57, fwereade wrote:
> Nope, this is just a straight-up error, I think. We don't have any way
of
> resolving it, or reporting it, it's true; but panicking won't improve
matters
> so... ;).
https://codereview.appspot.com/7385049/diff/7001/worker/uniter/uniter_test.go#newcode620
worker/uniter/uniter_test.go:620: // doing upgradeCharm before
addRelation (?!)
On 2013/02/25 10:31:57, fwereade wrote:
> This test does an add-relation as quickly as possible after an
upgrade-charm, in
> the hope that the scheduler will deliver the events in the wrong
order. The
> observed behaviour should be the same in either case.
Please take a look.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ modes.go uniter/ modes.go (right):
File worker/
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ modes.go# newcode145 uniter/ modes.go: 145: // handle the relations for the new unit
worker/
On 2013/02/25 10:31:57, fwereade wrote:
> Now the upgrade is complete, we'll need to check all relations again:
some might
> previously have been skipped (if they involved endpoints only
implemented in the
> new charm).
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter. go uniter/ uniter. go (right):
File worker/
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter. go#newcode383 uniter/ uniter. go:383: // possibly even panic?
worker/
On 2013/02/25 10:31:57, fwereade wrote:
> Nope, this is just a straight-up error, I think. We don't have any way
of
> resolving it, or reporting it, it's true; but panicking won't improve
matters
> so... ;).
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter. go#newcode383 uniter/ uniter. go:383: // possibly even panic?
worker/
On 2013/02/25 10:31:57, fwereade wrote:
> Nope, this is just a straight-up error, I think. We don't have any way
of
> resolving it, or reporting it, it's true; but panicking won't improve
matters
> so... ;).
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter. go#newcode389 uniter/ uniter. go:389: log.Printf( "worker/ uniter: ignoring not
worker/
implemented relation endpoint %q", ep)
On 2013/02/25 10:31:57, fwereade wrote:
> "skipping relation with unknown endpoint"?
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter_ test.go uniter/ uniter_ test.go (right):
File worker/
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter_ test.go# newcode323 uniter/ uniter_ test.go: 323: customize: func(c *C, path string, ctx
worker/
*context) {
On 2013/02/25 10:31:57, fwereade wrote:
> (c, ctx, path) feels neater to me, but YMMV
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter_ test.go# newcode620 uniter/ uniter_ test.go: 620: // doing upgradeCharm before
worker/
addRelation (?!)
On 2013/02/25 10:31:57, fwereade wrote:
> This test does an add-relation as quickly as possible after an
upgrade-charm, in
> the hope that the scheduler will deliver the events in the wrong
order. The
> observed behaviour should be the same in either case.
Done.
https:/ /codereview. appspot. com/7385049/ diff/7001/ worker/ uniter/ uniter_ test.go# newcode636 uniter/ uniter_ test.go: 636: waitHooks{ "db2-relation- joined mysql/0
worker/
db2:0"},
On 2013/02/25 10:31:57, fwereade wrote:
> May as well stick those steps together.
Done.
https:/ /codereview. appspot. com/7385049/