commit 89d532a8638427da9b195f0216272ee6063cd7c2
author Mike Burrows <m3b@google.com> Thu Jun 16 16:37:16 2016 -0700
committer Mike Burrows <m3b@google.com> Thu Jun 16 16:48:29 2016 -0700
tree b01e1c4a4e3271e8ca4c8714aedbdf647aef4cfa
parent ea91d68a91ad134a8de79f7531ef0cde37dfd169

v.io/v23/syncbase: call context.CancelFunc functions

In a previous cleanup, we made sure to call all context.CancelFunc
functions where we would otherwise leak memory.

The check in change 22953 is now more strict.  It enforces the spec of
Go's context package, which requires that the context.CancelFunc
be called, even if the context will be cancelled by other means.

This change fixes up the places in syncbase that the new check
reveals.

MultiPart: 1/2
Change-Id: I4b3671302f5916be1899342cdcacce70f3122b14