Updated to 1.7 (and accidentally also to 1.8), and after following the steps outlined here, this started happening. I’m not sure where this is going on or how to fix it, so I was hoping someone with experience might be able to see these error logs and help me pinpoint where I should be looking. I’ve looked through all of my code and nothing is ever set to undefined, so maybe it’s in a package of some sort?
W20190422-16:33:52.535(-3)? (STDERR) /Users/user_name/.meteor/packages/meteor-tool/.1.8.1.1k83ph4.d4ti++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:313
W20190422-16:33:52.535(-3)? (STDERR) throw(ex);
W20190422-16:33:52.535(-3)? (STDERR) ^
W20190422-16:33:52.536(-3)? (STDERR)
W20190422-16:33:52.536(-3)? (STDERR) MongoError: '$set' is empty. You must specify a field like so: {$set: {<field>: ...}}
W20190422-16:33:52.536(-3)? (STDERR) at Function.create (/Users/user_name/.meteor/packages/npm-mongo/.3.1.2.hanfom.kehlm++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb-core/lib/error.js:43:12)
W20190422-16:33:52.536(-3)? (STDERR) at toError (/Users/user_name/.meteor/packages/npm-mongo/.3.1.2.hanfom.kehlm++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb/lib/utils.js:149:22)
W20190422-16:33:52.536(-3)? (STDERR) at coll.s.topology.update (/Users/user_name/.meteor/packages/npm-mongo/.3.1.2.hanfom.kehlm++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb/lib/operations/collection_ops.js:1414:39)
W20190422-16:33:52.536(-3)? (STDERR) at /Users/user_name/.meteor/packages/npm-mongo/.3.1.2.hanfom.kehlm++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb-core/lib/connection/pool.js:532:18
W20190422-16:33:52.537(-3)? (STDERR) at _combinedTickCallback (internal/process/next_tick.js:132:7)
W20190422-16:33:52.537(-3)? (STDERR) at process._tickDomainCallback (internal/process/next_tick.js:219:9)