Meteor 0.9.4/1.0 Cannot update packages

295 views
Skip to first unread message

Matteo Saporiti

unread,
Oct 29, 2014, 10:02:18 AM10/29/14
to meteo...@googlegroups.com
Hi,
today I tried to update the webapp I'm working on to 1.0, the update project started but never finished.
I cloned the project on a clean machine, installed meteor and launched the update again, it got stuck again with node process using a full core (25% cpu) and with a VM-size that was out of the ordinary (I think the maximum it can be with 64 bit process).
I took a screenshot of that
















I went back to the other machine and tried updating the packages only (while keeping meteor 0.9.4), that failed too, but without the VM issue.

I'm not sure what's the problem, but it seems like there's something wrong with the packages.

The output from meteor list is:

accounts-base                1.1.2  A user account system
accounts-facebook            1.0.2  Login service for Facebook accounts
accounts-google              1.0.2  Login service for Google accounts
accounts-password            1.0.3* Password support for accounts
accounts-twitter             1.0.2  Login service for Twitter accounts
alanning:roles               1.2.13  Role-based authorization
altapp:urlify2-minifiable    1.1.0  Generate slugs with smart urlify supporti...
arunoda:npm                  0.2.6  complete npm integration/support for Meteor
arunoda:subs-manager         1.0.1  Subscriptions Manager for Meteor
bootstrap-3                  0.0.0  HTML, CSS, and JS framework for developin...
bootstrap3-confirmation      0.0.0
cmather:handlebars-server    2.0.0  Allows handlebars templates to be defined...
dandv:jquery-rateit          1.0.9* RateIt - a modern, mobile-friendly, jQuer...
email                        1.0.4  Send email messages
gadicohen:headers            0.0.25* Access HTTP headers on both server and c...
gadicohen:messageformat      0.0.45  MessageFormat support, the Meteor way
gadicohen:phantomjs          0.0.2  phantomjs installation script; wrapper fo...
gfk:notifications            1.0.11  Notifications - Add reactive notificatio...
iron:router                  0.9.4* Routing specifically designed for Meteor
jeeeyul:moment-with-langs    2.8.2* Moment with languages
jquery                       1.0.1  Manipulate the DOM using CSS selectors
less                         1.0.10* The dynamic stylesheet language
manuelschoebel:ms-seo        0.3.0  Easily config SEO for your routes
meteorhacks:inject-initial   1.0.2  Allow injection of arbitrary data to init...
meteorhacks:kadira           2.11.13  Performance Monitoring for Meteor
meteorhacks:npm              1.2.0  Use npm modules with your Meteor App
mrt:iron-router-progress     0.9.2  Progressbar for iron:router
npm-container                1.0.0  Contains all your npm dependencies
raix:handlebar-helpers       0.1.3  Handlebar helpers
rajit:bootstrap3-datepicker  1.3.1  Meteor packaging of eternicode/bootstrap-...
reactive-dict                1.0.4  Reactive dictionary
sacha:spin                   2.0.4  Simple spinner package for Meteor
spiderable                   1.0.4* Makes the application crawlable to web sp...
standard-app-packages        1.0.3  Moved to meteor-platform
underscore                   1.0.1  Collection of small helpers: _.map, _.eac...
veg-accounts-ui              0.0.0  veg-accounts-ui login widgets


(bootstrap-3 bootstrap3-confirmation and veg-account-ui are local packages).

Any help in finding the root cause of this issue would be really appreciated.

Thanks in advance.

Matteo

Valerio Santinelli

unread,
Oct 29, 2014, 11:00:14 AM10/29/14
to meteo...@googlegroups.com
Ciao Matteo :)

you should try and move away your local packages just to make sure it's got nothing to do with them. 

Looking at your screenshots it seems like it actually upgraded all the packages and the core Meteor distribution to the latest versions. 

What's happening if you just run meteor? Is your app spinning up?

Cheers!

Valerio Santinelli

Matteo Saporiti

unread,
Oct 30, 2014, 4:54:51 AM10/30/14
to meteo...@googlegroups.com
Ciao Valerio :)

I've removed the local packages and tried updating again.
Same result, cpu at 100% and process stuck.

If I run meteor the application works, but it still have part of the old packages (I think all the atmosphere one are old).

This are the packages list before doing anything (I'm copying the list from .meteor/version)

accoun...@1.1.2
accounts...@1.0.2
account...@1.0.2
account...@1.1.2
accounts...@1.0.3
accounts...@1.0.2
alanning:ro...@1.2.13
altapp:urlify2-m...@1.1.0
application-...@1.0.3
arunoda:n...@0.2.6
arunoda:subs-m...@1.0.1
autou...@1.1.2
bas...@1.0.1
binar...@1.0.1
blaze...@1.0.1
bl...@2.0.2
boilerplat...@1.0.1
boots...@0.0.0
bootstrap3-...@0.0.0
callba...@1.0.1
ch...@1.0.2
cmather:handleba...@2.0.0
coffee...@1.0.4
ctl-h...@1.0.4
c...@1.0.2
dandv:jquery...@1.0.9
d...@1.0.10
de...@1.0.5
ej...@1.0.4
em...@1.0.4
face...@1.1.1
fast...@1.0.1
follower...@1.0.2
gadicohen:hea...@0.0.25
gadicohen:messag...@0.0.45
gadicohen:phan...@0.0.2
geojso...@1.0.1
gfk:notifi...@1.0.11
goo...@1.1.1
handl...@1.0.1
html-...@1.0.2
htm...@1.0.2
ht...@1.0.7
id-...@1.0.1
iron:co...@0.3.4
iron:dynamic-...@0.4.1
iron:lay...@0.4.1
iron:rou...@0.9.4
jeeeyul:moment-w...@2.8.2
jqu...@1.0.1
js...@1.0.1
le...@1.0.10
live...@1.0.11
locals...@1.0.1
log...@1.0.4
manuelschoebel:ms-...@0.3.0
meteor-...@1.1.2
met...@1.1.2
meteorhacks:as...@1.0.0
meteorhacks:inject-...@1.0.2
meteorhacks:kadira-bi...@1.2.0
meteorhacks:kad...@2.11.13
meteorhacks:met...@1.2.0
meteorhacks:n...@1.2.0
mini...@1.1.1
mini...@1.0.4
mobile-s...@1.0.1
mongo-l...@1.0.6
mo...@1.0.7
mrt:iron-route...@0.9.2
npm-b...@0.7.7
npm-co...@1.0.0
oau...@1.1.1
oau...@1.1.1
oa...@1.1.1
observe-...@1.0.3
ordere...@1.0.1
raix:handleba...@0.1.3
rajit:bootstrap3...@1.3.1
ran...@1.0.1
reacti...@1.0.4
reacti...@1.0.3
rel...@1.1.1
re...@1.0.1
route...@1.0.2
sacha:sp...@2.0.4
service-co...@1.0.2
ses...@1.0.3
s...@1.0.1
spacebars...@1.0.3
spac...@1.0.3
spide...@1.0.4
s...@1.0.1
standard-a...@1.0.3
templ...@1.0.8
tra...@1.0.3
twi...@1.1.1
u...@1.0.4
under...@1.0.1
u...@1.0.1
veg-acc...@0.0.0
webapp-...@1.0.1
web...@1.1.3


This is after removing the local ones and updating to 1.0


accoun...@1.1.2
accounts...@1.0.2
account...@1.0.2
account...@1.1.2
accounts...@1.0.4
accounts...@1.0.2
alanning:ro...@1.2.13
altapp:urlify2-m...@1.1.0
application-...@1.0.3
arunoda:n...@0.2.6
arunoda:subs-m...@1.0.1
autou...@1.1.3
bas...@1.0.1
binar...@1.0.1
blaze...@1.0.1
bl...@2.0.3
boilerplat...@1.0.1
callba...@1.0.1
ch...@1.0.2
cmather:handleba...@2.0.0
coffee...@1.0.4
ctl-h...@1.0.4
c...@1.0.2
dandv:jquery...@1.0.22_2
d...@1.0.11
de...@1.0.5
ej...@1.0.4
em...@1.0.4
face...@1.1.2
fast...@1.0.1
follower...@1.0.2
gadicohen:hea...@0.0.25
gadicohen:messag...@0.0.45
gadicohen:phan...@0.0.2
geojso...@1.0.1
gfk:notifi...@1.0.11
goo...@1.1.2
handl...@1.0.1
html-...@1.0.2
htm...@1.0.2
ht...@1.0.8
id-...@1.0.1
iron:co...@0.3.4
iron:dynamic-...@0.4.1
iron:lay...@0.4.1
iron:rou...@0.9.4
jeeeyul:moment-w...@2.8.3
jqu...@1.0.1
js...@1.0.1
launch...@1.0.0
le...@1.0.11
live...@1.0.11
locals...@1.0.1
log...@1.0.5
manuelschoebel:ms-...@0.3.0
meteor-...@1.2.0
met...@1.1.3
meteorhacks:as...@1.0.0
meteorhacks:inject-...@1.0.2
meteorhacks:kadira-bi...@1.2.0
meteorhacks:kad...@2.11.13
meteorhacks:met...@1.2.0
meteorhacks:n...@1.2.0
mini...@1.1.2
mini...@1.0.5
mobile-s...@1.0.1
mongo-l...@1.0.6
mo...@1.0.8
mrt:iron-route...@0.9.2
npm-b...@0.7.7
npm-co...@1.0.0
oau...@1.1.2
oau...@1.1.1
oa...@1.1.2
observe-...@1.0.3
ordere...@1.0.1
raix:handleba...@0.1.3
rajit:bootstrap3...@1.3.1
ran...@1.0.1
reacti...@1.0.4
reacti...@1.0.3
rel...@1.1.1
re...@1.0.1
route...@1.0.2
sacha:sp...@2.0.4
service-co...@1.0.2
ses...@1.0.4
s...@1.0.1
spacebars...@1.0.3
spac...@1.0.3
spide...@1.0.5
s...@1.0.1
standard-a...@1.0.3
templ...@1.0.9
tra...@1.0.3
twi...@1.1.2
u...@1.0.4
under...@1.0.1
u...@1.0.2
webapp-...@1.0.1
web...@1.1.4


And iron-router, kadira and headers have new versions up.
 
And I'm not able to add any other packages because if I try the result is always
 

Valerio Santinelli

unread,
Oct 30, 2014, 6:53:44 AM10/30/14
to meteo...@googlegroups.com
Ciao Matteo,

it looks like it might be a problem with the dependency solver, but it's kind of hard to debug without access to the source code. Is that project Open Source and available anywhere by any chance?
Can you paste the content of your .meteor/packages?

Valerio Santinelli


Il giorno giovedì 30 ottobre 2014 09:54:51 UTC+1, Matteo Saporiti ha scritto:
Ciao Valerio :)

I've removed the local packages and tried updating again.
Same result, cpu at 100% and process stuck.

If I run meteor the application works, but it still have part of the old packages (I think all the atmosphere one are old).

This are the packages list before doing anything (I'm copying the list from .meteor/version)

accoun...@1.1.2
accounts...@1.0.2
account...@1.0.2
account...@1.1.2
accounts...@1.0.3
accounts...@1.0.2
alanning:ro...@1.2.13
altapp:urlify2-minifiable@1.1.0
application-configuration@1.0.3

arunoda:n...@0.2.6
arunoda:subs-m...@1.0.1
autou...@1.1.2
bas...@1.0.1
binar...@1.0.1
blaze...@1.0.1
bl...@2.0.2
boilerplat...@1.0.1
boots...@0.0.0
bootstrap3-...@0.0.0
callba...@1.0.1
ch...@1.0.2
cmather:handlebars-server@2.0.0
jeeeyul:moment-with-langs@2.8.2

jqu...@1.0.1
js...@1.0.1
le...@1.0.10
live...@1.0.11
locals...@1.0.1
log...@1.0.4
manuelschoebel:ms-...@0.3.0
meteor-...@1.1.2
met...@1.1.2
meteorhacks:as...@1.0.0
meteorhacks:inject-initial@1.0.2
meteorhacks:kadira-binary-de...@1.2.0

meteorhacks:kad...@2.11.13
meteorhacks:met...@1.2.0
meteorhacks:n...@1.2.0
mini...@1.1.1
mini...@1.0.4
mobile-s...@1.0.1
mongo-l...@1.0.6
mo...@1.0.7
mrt:iron-route...@0.9.2
npm-b...@0.7.7
npm-co...@1.0.0
oau...@1.1.1
oau...@1.1.1
oa...@1.1.1
observe-...@1.0.3
ordere...@1.0.1
raix:handleba...@0.1.3
rajit:bootstrap3-datepicker@1.3.1
altapp:urlify2-minifiable@1.1.0
application-configuration@1.0.3

arunoda:n...@0.2.6
arunoda:subs-m...@1.0.1
autou...@1.1.3
bas...@1.0.1
binar...@1.0.1
blaze...@1.0.1
bl...@2.0.3
boilerplat...@1.0.1
callba...@1.0.1
ch...@1.0.2
cmather:handlebars-server@2.0.0
jeeeyul:moment-with-langs@2.8.3

jqu...@1.0.1
js...@1.0.1
launch...@1.0.0
le...@1.0.11
live...@1.0.11
locals...@1.0.1
log...@1.0.5
manuelschoebel:ms-...@0.3.0
meteor-...@1.2.0
met...@1.1.3
meteorhacks:as...@1.0.0
meteorhacks:inject-initial@1.0.2
meteorhacks:kadira-binary-de...@1.2.0

meteorhacks:kad...@2.11.13
meteorhacks:met...@1.2.0
meteorhacks:n...@1.2.0
mini...@1.1.2
mini...@1.0.5
mobile-s...@1.0.1
mongo-l...@1.0.6
mo...@1.0.8
mrt:iron-route...@0.9.2
npm-b...@0.7.7
npm-co...@1.0.0
oau...@1.1.2
oau...@1.1.1
oa...@1.1.2
observe-...@1.0.3
ordere...@1.0.1
raix:handleba...@0.1.3
rajit:bootstrap3-datepicker@1.3.1

Matteo Saporiti

unread,
Oct 30, 2014, 8:02:21 AM10/30/14
to meteo...@googlegroups.com
Ciao,

unfortunately the project is not open source so I can't post here a link to the code.
The content of .meteor/packages is

# Meteor packages used by this project, one per line.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.

standard-app-packages
jquery
alanning:roles
manuelschoebel:ms-seo
accounts-base
accounts-password
accounts-twitter
arunoda:npm
gadicohen:headers
jeeeyul:moment-with-langs
accounts-facebook
accounts-google
sacha:spin
dandv:jquery-rateit
email

mrt:iron-router-progress
gfk:notifications
less
raix:handlebar-helpers
meteorhacks:kadira
arunoda:subs-manager
underscore
meteorhacks:npm


npm-container
rajit:bootstrap3-datepicker
cmather:handlebars-server
reactive-dict
spiderable
iron:router
gadicohen:phantomjs
gadicohen:messageformat
meteorhacks:inject-initial
altapp:urlify2-minifiable

I can probably start a new project and add the same reference, and see if something breaks, but that still wouldn't solve the problem.
Is there no way to have meteor print everything is doing during an update?

Valerio Santinelli

unread,
Oct 30, 2014, 8:26:35 AM10/30/14
to meteo...@googlegroups.com
What I can tell you is that if you take this and put it in a new project, you end up with the same problem.

You can safely remove arunoda:npm as you already include meteorhacks:npm which is the correct package.

The package that is causing the infinite wait time for the resolution of dependencies is iron:router. If you comment that one out, a meteor update will work.

Now the real task is to figure out what package is conflicting with iron:router. 

I hope this can help you a little bit.

Ciao!

Valerio Santinelli

Matteo Saporiti

unread,
Oct 30, 2014, 11:49:47 AM10/30/14
to meteo...@googlegroups.com
Thanks for the help!

The workaround to "bypass" the issue is to remove iron:router, update everything and finally add iron:router again.

When I have a bit of time I'll try to understand what's causing the problem.
Still, a flag to debug the update command would really streamline the process (as the number of packages grow this issue may appear more often).

Valerio Santinelli

unread,
Oct 30, 2014, 12:05:56 PM10/30/14
to meteo...@googlegroups.com
I've opened an issue at Meteor's repo https://github.com/meteor/meteor/issues/2968 just in case.

Valerio Santinelli
Reply all
Reply to author
Forward
0 new messages