Meteor 1.4.2.1 is an important patch for 1.4.2 users

massimosgrelli · November 10, 2016, 9:56am

Well, before it was working for me with 1.4.2, I had babel-runtime version 0.1.13. Now I did upgrade to 1.4.2.1 but now I see babel-runtime 1.0.0 and meteor doesn’t start any more:

W20161110-10:47:39.012(1)? (STDERR) /home/max/src/mob/.meteor/local/build/programs/server/boot.js:348
W20161110-10:47:39.102(1)? (STDERR) }).run();
W20161110-10:47:39.102(1)? (STDERR)    ^
W20161110-10:47:39.103(1)? (STDERR) 
W20161110-10:47:39.103(1)? (STDERR) Error: The babel-runtime npm package could not be found in your node_modules 
W20161110-10:47:39.104(1)? (STDERR) directory. Please run the following command to install it:
W20161110-10:47:39.105(1)? (STDERR) 
W20161110-10:47:39.106(1)? (STDERR)   meteor npm install --save babel-runtime
W20161110-10:47:39.107(1)? (STDERR) 
W20161110-10:47:39.107(1)? (STDERR)     at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)
W20161110-10:47:39.108(1)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:181:9)
W20161110-10:47:39.109(1)? (STDERR)     at require (packages/modules-runtime.js:106:16)
W20161110-10:47:39.110(1)? (STDERR)     at packages/babel-runtime.js:139:15
W20161110-10:47:39.110(1)? (STDERR)     at packages/babel-runtime.js:150:3
W20161110-10:47:39.111(1)? (STDERR)     at /home/max/src/mob/.meteor/local/build/programs/server/boot.js:295:34
W20161110-10:47:39.111(1)? (STDERR)     at Array.forEach (native)
W20161110-10:47:39.112(1)? (STDERR)     at Function._.each._.forEach (/home/max/.meteor/packages/meteor-tool/.1.4.2_1.scvu6x++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)
W20161110-10:47:39.113(1)? (STDERR)     at /home/max/src/mob/.meteor/local/build/programs/server/boot.js:128:5
W20161110-10:47:39.114(1)? (STDERR)     at /home/max/src/mob/.meteor/local/build/programs/server/boot.js:344:5
```

xriu · November 10, 2016, 9:57am

execute

meteor npm install --save babel-runtime

massimosgrelli · November 10, 2016, 9:58am

I did and:

max@loki:~/src/mob$ meteor npm install --save babel-runtime
npm WARN saveError ENOENT: no such file or directory, open '/home/max/src/mob/package.json'
/home/max/src/mob
└─┬ babel-runtime@6.18.0 
  ├── core-js@2.4.1 
  └── regenerator-runtime@0.9.6 

npm WARN enoent ENOENT: no such file or directory, open '/home/max/src/mob/package.json'
npm WARN mob No description
npm WARN mob No repository field.
npm WARN mob No README data
npm WARN mob No license field.
```

massimosgrelli · November 10, 2016, 10:03am

SOLVED. Stop Meteor, then install babel-runtime, then start meteor again.

tidee · November 10, 2016, 11:28am

Ran meteor update and got the following errors:

/home/my_project/.meteor/packages/meteor-tool/.1.4.2_1.crv9df++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/isopackets/ddp/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:190
      throw error;
      ^

Error: EACCES: permission denied, mkdir '/home/my_project/.meteor/packages/aldeed_schema-index/.build878350..1.1.1.15mxsfl++os+web.browser+web.cordova'

Tried to run as sudo meteor update, but it is suggesting that this is not what I want to be doing. Note: I made sure I used the suggested chown command following the attempt to use sudo meteor update.

fbsn · November 10, 2016, 12:36pm

I’ve followed the steps, but I’m still having the issue described here: Meteor not detecting new files

Sadly, I won’t be able to update to this version.

kulttuuri · November 10, 2016, 12:44pm

Looks like there is quite big performance issue with the latest meteor version. I just updated by executing these two commands:

meteor update
meteor npm install --save babel-runtime

With meteor 1.4.2 my node cpu usage when idle has been on OS X activity monitor between 2-3%. Now with latest 1.4.2.1 cpu usage is between 4-6.2%. I’ve now downgraded back to 1.4.2 and the cpu issue went away.

My colleague also just installed the latest version on he’s windows 10 computer by running those two same commands and he’s cpu usage idle on 1.4.2 was 0-3%, now with latest 1.4.2.1 it’s 5-10%.

We both inspected the cpu usage for around 5 minutes.

valentinvichnal · November 10, 2016, 2:41pm

I have the same CPU issue on Windows 8.1

A simple 1.4.2 meteor app cpu usage was between 5-10%
after the upated to 1.4.2.1 the same app cpu usage now above 50% and became very slow.

veered · November 11, 2016, 12:21am

Are you noticing slower reloads or anything? It doesn’t really feel like a couple percent bump in CPU usage is that big of a deal in dev…

kulttuuri · November 11, 2016, 7:14am

I’m mostly afraid that this issue persists in production, that’s why I didn’t want to push the latest version to galaxy yet. Haven’t checked back with that yet.

Is there a command that I can pass to meteor to inspect the total build / reload times? If the cpu usage increase is just for dev and it increases the reload times, that sounds like a good tradeoff

adamginsburg · November 11, 2016, 7:53am

Having issues running that babel install… any ideas pls?

Also I am now getting security issues on Cordova app installed on my physical phone, have App.accessRules changed with this release??? It was working fine with 1.4.2 rc 2

For example, I have the following in my mobile-conflg …

App.accessRule('https://*.stripe.com/*', { type: 'navigation' } );
App.accessRule('https://*.filepicker.com/*', { type: 'navigation' } );
App.accessRule('https://*.filestackcontent.com/*', { type: 'navigation' } );
App.accessRule('https://*.filepicker.io/*', { type: 'navigation' } );
App.accessRule('https://*.filestack.io/*', { type: 'navigation' } );
App.accessRule('https://*.facebook.com/*', { type: 'navigation' } );

But I am getting lots of Failed to load resources from those domains. Again, this was all working fine with 1.4.2 on the document.on error…

Any thoughts appreciated???

BTW, my XCode seems to have been upgraded to 8.1, so not sure if some new setting in that as it seems to get running on my iOS emulator, so this just seems related to running on my physical devices (via lightning cable).

vjau · November 11, 2016, 7:57am

Same issue on Linux.
1.4.2 give me cpu usage around 4-6%
1.4.2.1 is around 10-13%
@benjamn is it normal ?

mrvudoan · November 11, 2016, 2:22pm

Pls help, it seems to be stuck hours at ‘Extracting meteor-tool@1.4.2_1…’.

kvetoslav · November 11, 2016, 8:56pm

I have the same CPU issue on Linux.

benjamn · November 11, 2016, 9:19pm

You can try running METEOR_DISABLE_FS_FIBERS=false meteor to see if the CPU usage is related to the increased use of synchronous file system operations in Meteor 1.4.2.1—a performance optimization that has improved rebuild performance for many users.

benjamn · November 11, 2016, 9:20pm

Try METEOR_PROFILE=20 meteor, though that won’t measure idle CPU usage, just the timings of various parts of the build process.

mrvudoan · November 11, 2016, 10:37pm

I gave up at last. Just uninstall the meteor and then reinstall it. Have the last version now.

guidouil · November 12, 2016, 8:29am

Since the update I get strange messages in the console client side

Exception in template helper: Error
    at exports.check (http://localhost:3000/packages/check.js?hash=d4de24f57efd5d716b6ce9a7a90bf6a91b307bf4:67:15)
    at Object.<anonymous> (http://localhost:3000/app/app.js?hash=f539d4f234ce1ef54e997cf9351729d9aa12f3ee:37039:5)
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3035:16
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:1697:16
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3087:66
    at Function.Template._withTemplateInstanceFunc (http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3728:12)
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3086:27
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:172:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:106:25)
    at Object.Spacebars.mustache (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:110:39)

There seem’s to be an error with the check function but to figure it out is outta my league
(the app still work fine though and yes I did installed the required babel-runtime)
Can somebody throw me a bone here ?
Thanks

praydays · November 12, 2016, 3:01pm

I download the officially provided InstallMeteor.exe and install it in China, but it failed from time to time.
The speed of downloading Meteor during installing is much slower than ever before. Why so ?

Is there any offline-installer provided for Meteor?
Thanks.

kulttuuri · November 14, 2016, 1:54pm

Tried now, same higher cpu usage with that parameter true or false. However I believe this cpu increase happens only in development environment (hopefully) for better rebuild times so I’ll take a stab on updating my production servers with the latest version.