Meteor update 1.5.4.2 --> 1.8 findings

[matleppa]

no data in application

1. clone platform (meteor 1.5)
2. fetch upgrade branch (meteor 1.8)

Succeeds after installation of some packages.

some data in application

1. clone platform
2. provide APIs, Organizations, Users
3. fetch upgrade branch

What happens:

[matleppa]

Messages

Your app has been updated to Meteor 1.8.0.2 from Meteor 1.5.2. Restart meteor to use the new release.

11:04:25.67 C:\Users\leppanen\apinf\platform_meteor_180\platform>meteor [[[[[ C:\Users\leppanen\apinf\platform_meteor_180\platform ]]]]]

=> Started proxy.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Unable to resolve some modules:

"@babel/runtime/helpers/interopRequireDefault" in /C/Users/leppanen/apinf/platform_meteor_180/platform/apinf_packages/core/client/lib/chartsjs/d3.js (web.browser.legacy) "@babel/runtime/helpers/typeof" in /C/Users/leppanen/apinf/platform_meteor_180/platform/apinf_packages/core/client/lib/chartsjs/d3.js (web.browser.legacy) "@babel/runtime/helpers/inheritsLoose" in /C/Users/leppanen/apinf/platform_meteor_180/platform/apinf_packages/mqtt_dashboard/client/topics/page/search_helpers.js (web.browser.legacy)

If you notice problems related to these missing modules, consider running:

meteor npm install --save @babel/runtime

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting. Can't start Mongo server.

11:09:13.77 C:\Users\leppanen\apinf\platform_meteor_180\platform>

[matleppa]

Installed at first babel

11:09:13.77 C:\Users\leppanen\apinf\platform_meteor_180\platform>meteor npm install --save @babel/runtime npm WARN deprecated [email protected]: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated [email protected]: This version is no longer maintained. Please upgrade to the latest version.

[email protected] install C:\Users\leppanen\apinf\platform_meteor_180\platform\node_modules\chimp\node_modules\fibers node build.js || nodejs build.js

11:21:19.57 C:\Users\leppanen\apinf\platform_meteor_180\platform\node_modules\chimp\node_modules\fibers>if not defined npm_config_node_gyp (node "C:\Users\leppanen\AppData\Local.meteor\packages\meteor-tool\1.8.0_2\mt-os.windows.x86_64\dev_bundle\lib\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild --release ) else (node "C:\Users\leppanen\AppData\Local.meteor\packages\meteor-tool\1.8.0_2\mt-os.windows.x86_64\dev_bundle\lib\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild --release ) Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. C:\Users\leppanen\apinf\platform_meteor_180\platform\node_modules\chimp\node_modules\fibers\build\fibers.vcxp roj(20,3): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that t he path in the <Import> declaration is correct, and that the file exists on disk. gyp ERR! build error gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\Users\leppanen\AppData\Local.meteor\packages\meteor-tool\1.8.0_2\mt-os.windows.x86_64\dev_bundle\lib\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Windows_NT 10.0.17134 gyp ERR! command "C:\Users\leppanen\AppData\Local\.meteor\packages\meteor-tool\1.8.0_2\mt-os.windows.x86_64\dev_bundle\bin\node.exe" "C:\Users\leppanen\AppData\Local\.meteor\packages\meteor-tool\1.8.0_2\mt-os.windows.x86_64\dev_bundle\lib\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--release" gyp ERR! cwd C:\Users\leppanen\apinf\platform_meteor_180\platform\node_modules\chimp\node_modules\fibers gyp ERR! node -v v8.11.4 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok node-gyp exited with code: 1 Please make sure you are using a supported platform and node version. If you would like to compile fibers on this machine please make sure you have setup your build environment-- Windows + OS X instructions here: https://github.com/nodejs/node-gyp Ubuntu users please run: sudo apt-get install g++ build-essential Alpine users please run: sudo apk add python make g++ 'nodejs' is not recognized as an internal or external command, operable program or batch file. npm WARN The package JSONStream is included as both a dev and production dependency. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: node build.js || nodejs build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\leppanen\AppData\Roaming\npm-cache_logs\2019-02-01T09_21_24_908Z-debug.log

11:21:25.01 C:\Users\leppanen\apinf\platform_meteor_180\platform>

[matleppa]

New attempt to start meteor

11:21:25.01 C:\Users\leppanen\apinf\platform_meteor_180\platform>meteor [[[[[ C:\Users\leppanen\apinf\platform_meteor_180\platform ]]]]]

=> Started proxy.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting.

Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/

Unexpected mongo exit code 62. Restarting. Can't start Mongo server.

11:25:09.35 C:\Users\leppanen\apinf\platform_meteor_180\platform>

[matleppa]

check database engine

meteor:PRIMARY> db.version() 3.2.15

meteor:PRIMARY> db.serverStatus().storageEngine { "name" : "mmapv1", "supportsCommittedReads" : false, "persistent" : true }

.meteor\packages [email protected]