TO_PAT: breaks test server; important?
FAILING TEST: should update receiver
don't shadow invocation this; mcm 1.1.4
fix for Meteor 0.9.4
Hack fix to tell meteor to not be so complaining about out methods on Template.prototype
slightly more elegant hack to the meteor 0.9.4 complaining
add addedObject(), removeObject(), changedObject() to make it more natural to work with a client-side only cursor.

also make thatManager on the cursor not enumerable. ( maybe this is where the circular reference that kadira is complaining about )
make some functions that are on dbObject.prototype also available on dbObject
replace 'createSubClass' with 'create'
inc version
handle null clientObject - _.pick() does not expect object to be null
fix single argument case for upsertFromUntrusted
TO_PAT: reply
upserFromuntrust now only takes 1 paramtr
Merge remote-tracking branch 'refs/remotes/origin/master'
TO_PAT_DMR: Temporary disable this check, since it needs to be better throughout through. Here are 2 cases that I saw:
1. If checking !_.isEmpty, research request upsert will fail. Removing ! makes most of the calls works. Except the cases 2.
2. ResearcherManager.updatePortfolioReport failed since it only passed an object with {forcedValues: {humanId:humanId, portfolioProjectType: PortfolioProjectType.report}}. By executing _.omit it’s empty.
Revert "TO_PAT_DMR: Temporary disable this check, since it needs to be better throughout through. Here are 2 cases that I saw:"

This reverts commit b5835b473490cea101fde1c116fa501094c7f8fe.
allow 'clientObj' as an option to upsertFromUntrusted
wrap
TO_PAT: test.throws