OK installer should work now.
Woo hoo! Congratulations to the Meteor team and everyone! Got to celebrate that!
Does it scale now?
2 Likes
i heard if it’s slower people spend more time on your site, so it’s a feature!
8 Likes
Do the build time improvements also apply for Windows?
Wow! Great job MDG team on 1.2! Just fired it up and started writing ES2015 wohoo! Added React and decided to remove Blaze and Session, love the more modular core! You guys rock 
4 Likes
@sashko I’m getting bugs with the new version. Steps to replicate (on Mac OS):
meteor create app
cd app
meteor 
I20150922-13:21:39.515(10)? Internal exception while processing message { msg: 'connect',
I20150922-13:21:39.516(10)? version: '1',
I20150922-13:21:39.517(10)? support: [ '1', 'pre2', 'pre1' ] } Cannot read property '_CurrentInvocation' of undefined TypeError: Cannot read property '_CurrentInvocation' of undefined
I20150922-13:21:39.517(10)? at withoutInvocation (packages/meteor/packages/meteor.js:404:1)
I20150922-13:21:39.517(10)? at bindAndCatch (packages/meteor/packages/meteor.js:414:1)
I20150922-13:21:39.517(10)? at Object._.extend.setInterval (packages/meteor/packages/meteor.js:441:1)
I20150922-13:21:39.517(10)? at [object Object]._.extend._startHeartbeatIntervalTimer (packages/ddp-common/packages/ddp-common.js:71:1)
I20150922-13:21:39.517(10)? at [object Object]._.extend.start (packages/ddp-common/packages/ddp-common.js:66:1)
I20150922-13:21:39.517(10)? at new Session (livedata_server.js:312:20)
I20150922-13:21:39.517(10)? at [object Object]._.extend._handleConnect (livedata_server.js:1427:29)
I20150922-13:21:39.518(10)? at livedata_server.js:1356:18
1 Like
Continuing the discussion from Public release candidate of Meteor 1.2:
What happens if you do meteor update ?
Same thing happens after running meteor update
same here.
meteor create test
cd test
meteor
I20150921-21:29:51.325(-7)? Internal exception while processing message { msg: ‘connect’,
I20150921-21:29:51.326(-7)? version: ‘1’,
I20150921-21:29:51.326(-7)? support: [ ‘1’, ‘pre2’, ‘pre1’ ] } Cannot read property 'CurrentInvocation’ of undefined TypeError: Cannot read property 'CurrentInvocation’ of undefined
I20150921-21:29:51.326(-7)? at withoutInvocation (packages/meteor/packages/meteor.js:404:1)
I20150921-21:29:51.326(-7)? at bindAndCatch (packages/meteor/packages/meteor.js:414:1)
I20150921-21:29:51.326(-7)? at Object..extend.setInterval (packages/meteor/packages/meteor.js:441:1)
I20150921-21:29:51.326(-7)? at [object Object]..extend.startHeartbeatIntervalTimer (packages/ddp-common/packages/ddp-common.js:71:1)
I20150921-21:29:51.326(-7)? at [object Object]..extend.start (packages/ddp-common/packages/ddp-common.js:66:1)
I20150921-21:29:51.326(-7)? at new Session (livedata_server.js:312:20)
I20150921-21:29:51.326(-7)? at [object Object]._.extend._handleConnect (livedata_server.js:1427:29)
I20150921-21:29:51.326(-7)? at livedata_server.js:1356:18
Ok I will try this, looks like not everyone is getting this error though. Would you mind opening an issue on github? Forum threads are not the best place for tracking down bugs
They should. The idea now is that meteor should only rebuild the files that changed rather than everything at once.
Worked perfect for me when running meteor update.
Did it about an hour ago.
Update to 1.2-rc.17 -> checking whats changed in the commits, see 1.2-rc-18 -> (sigh) -> update to 1.2-rc.18 -> rc19?! WAAA -> check again -> HOLY COW RELEASE 1.2 !!!
Thanks for the update 
Lots of love 
Haha the RCs are like asymptotic to the actual release date, since we make tiny changes and release again when we find issues.
I just updated my current application on my Macbook Air, and everything went ok. Then I upgraded on my iMac, and the same error appeared as was mentioned a few comments above:
W20150922-07:47:37.158(2)? (STDERR) /Users/crea/.meteor/packages/meteor-tool/.1.1.7.1ni1b7++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20150922-07:47:37.159(2)? (STDERR) throw(ex);
W20150922-07:47:37.159(2)? (STDERR) ^
W20150922-07:47:37.198(2)? (STDERR) TypeError: Cannot read property '_CurrentInvocation' of undefined
W20150922-07:47:37.198(2)? (STDERR) at withoutInvocation (packages/meteor/packages/meteor.js:404:1)
W20150922-07:47:37.198(2)? (STDERR) at bindAndCatch (packages/meteor/packages/meteor.js:414:1)
W20150922-07:47:37.198(2)? (STDERR) at Object._.extend.defer (packages/meteor/packages/meteor.js:469:1)
W20150922-07:47:37.199(2)? (STDERR) at [object Object].MongoConnection.tail (packages/mongo/packages/mongo.js:1136:1)
W20150922-07:47:37.199(2)? (STDERR) at [object Object]._.extend._startTailing (packages/mongo/packages/mongo.js:1602:1)
W20150922-07:47:37.199(2)? (STDERR) at new OplogHandle (packages/mongo/packages/mongo.js:1441:1)
W20150922-07:47:37.199(2)? (STDERR) at new MongoConnection (packages/mongo/packages/mongo.js:224:1)
W20150922-07:47:37.199(2)? (STDERR) at new MongoInternals.RemoteCollectionDriver (packages/mongo/packages/mongo.js:3353:1)
W20150922-07:47:37.199(2)? (STDERR) at Object.<anonymous> (packages/mongo/packages/mongo.js:3387:1)
W20150922-07:47:37.199(2)? (STDERR) at Object.defaultRemoteCollectionDriver (packages/underscore/packages/underscore.js:779:1)
Reverting back to 1.1.0.3 works, though.
Here’s the issue thread: https://github.com/meteor/meteor/issues/5228
We know about the issue; reinstalling will fix it immediately; we are working on a new release that won’t have the issue at all.
meteor update fixed the problem right here
Any changes that can affect scalability at all?
Yes there are some improvements to live query - see the blog post, more details incoming!
2 Likes
I’m guessing that this “only build what has changed” is not entirely working or I’m just doing something silly.
Just started a brand new project, and any change will take 10 seconds at least. Not sure if that was the goal though (kudos if it was 
)… I did mention it before in this thread.
It feels like the rebuild speed is depending on network (internet) speed as well. Is it checking something online on each build maybe?