Yay! Congrats. Love all the news and updates coming down the pipeline.
10 Likes
This is great! 
3 Likes
So when will it be out ?
my meteor update still tells me This project is already at Meteor 1.8.3, the latest release.
Also this page still mention the 1.8.2 version as current 
That is because it does not have yet the “recommended” status. Run meteor update --release 1.9 and it should work just fine.
6 Likes
Great work - many thanks to all contributors!
It seemed to work with hiccups for me so I put it out on production yesterday.
2 Likes
Meteor 1.9 is now recommended
31 Likes
If I update to 1.9 but I am running node 8 on my EC2 server do I need to update my node on my EC2 to 12 first??
1 Like
Yes. The bundle won’t run properly if the the Node version doesn’t mach.
1 Like
Now i’m on 1.8.1, do you know if update to 1.9 we have to follow all “Migration Steps” ? (to 1.8.2 and 1.8.3 ? 1.9 have nothing to do)
You don’t need to upgrade incrementally, however, make sure you read about major changes / breaking changes between versions.
1 Like
IIRC node 12 is 64-bit only so 64-bit hardware is now required. Otherwise, because of Meteor’s emphasis on backward compatibility, there are usually no breaking changes.
Bcrypt doesn’t build with 1.9 
I had to revert back to 1.8.x until I can find a solution.
2 Likes
What is the process that a version goes through to become recommended ?
You probably just need to update the version of bcrypt you’re using in package.json
2 Likes
Great job on the new version.
For those using apollo there was some difficulties to update (at least for me) but Ben solved it on github with a new apollo package. Easiest way to fix it:
meteor remove apollo
meteor update
meteor add apollo
2 Likes
Sorry but Meteor 1.9 seems a bit rushed and not tested in it’s entire system to me as we have at least two major issues!
- We do get a transaction aborted issue that is replicable and doesn’t happen on Meteor 1.8.3 - this is obviously on the same code base and data.
MongoError: Transaction 1 has been aborted. .meteor/packages/promise/.0.11.2.76ph0.tuy1og++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/fiber_pool.js:43:40 .meteor/packages/promise/.0.11.2.76ph0.tuy1og++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/promise_server.js:56:12) .meteor/packages/promise/.0.11.2.76ph0.tuy1og++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/fiber_pool.js:43:40
- Meteor 1.9 is dramatically slower
While I don’t cover the specific times for MongoDb operations only, when our app performs it usual MongoDb heavy operations (meaning over 100 operations for a single call from frontend) I do see the following dramatic differences in timings (total runtime!)
This is directly from out logging file, same functions are called (both 1.8.3 and 1.9 produce the same results at least - hence “notMatching”):
Meteor 1.8.3:
notMatching in 2705ms
notMatching in 2838ms
notMatching in 2634ms
notMatching in 2532ms
notMatching in 3860ms
notMatching in 2743ms
notMatching in 3447ms
notMatching in 3266ms
notMatching in 3253ms
notMatching in 2667ms
Meteor 1.9 (1st run):
notMatching in 11606ms
notMatching in 9879ms
notMatching in 8560ms
notMatching in 9868ms
notMatching in 7038ms
notMatching in 10011ms
notMatching in 9913ms
notMatching in 8486ms
notMatching in 4966ms
notMatching in 6141ms
Meteor 1.9 (2nd run):
notMatching in 9280ms
notMatching in 7824ms
notMatching in 4732ms
notMatching in 6573ms
notMatching in 15214ms
notMatching in 8195ms
notMatching in 7930ms
notMatching in 6177ms
notMatching in 10416ms
notMatching in 11796ms
While this is calling a 3rd party API and surely is influencing the overall times please note that this happens at US night time (the server is in the US and over 70% of the 3rd party users are from the US).
But the whole app feels sluggish, from the time it takes between clicking on a card (which starts the whole backend function) until the animation starts (which is send from backend to frontend confirming that the backend is working on it).
Is there something wrong with Fibers?
My update process from 1.8.3 was really smooth:
meteor update # the core to 1.9
meteor update --all-packages # all yet non-updated packages
rm -rf ./node_modules # remove modules
meteor npm outdated # check outdated npm packages
meteor npm install --save <...> # install all outdated
meteor # boom - it's running
No issues at all. I also had a very smooth update from 1.8.1 to 1.8.3 after all packages and npm modules were up to date.
5 Likes
We’ve not updated but I did see @koenlav comment on this issue which might be related to your problem. See this comment also
Thanks Mark for highlighting this. Seems related indeed.
Andreas
For who is using DDP-Apollo, I just made sure it also works with Meteor 1.9. (Or with node 12 to be more specific).
The latest version is 2.2.0. Enjoy!
5 Likes