-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot publish new version of package #2656
Comments
$ meteor publish
Refreshing package metadata. This may take a moment.
Reading package...
Figuring out the best package versions to use. This may take a moment.
downloading check at version 1.0.1-rc0 ... done
downloading webapp at version 1.1.2-rc0 ... done
downloading webapp-hashing at version 1.0.0-cordova1 ... done
Bundling source...
Creating package version...
Uploading source...
Publishing package version...
Bundling build...
Creating package build...
Uploading build...
Publishing package build...
Published ground:db, version 0.0.5
Done! Yeah, finally it worked - I'm closing this guessing it could have been the connection to the package server or something |
Bugger - I'm reopening this... I tried to publish another package and now got the same error: ~/dev/packages/ground-util
$ meteor publish
Refreshing package metadata. This may take a moment.
Reading package...
Figuring out the best package versions to use. This may take a moment.
Exception in stream error callback: Error: Network error: wss://packages.meteor.com/websocket: read ECONNRESET
at packages/ddp/stream_client_nodejs.js:161
at packages/ddp/stream_client_nodejs.js:151
at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108) @ekatek Any hints on where to investigate the reason for the issue? Thanks |
What does it look like with 0.9.3-rc5? (We changed some bugs&output, might
|
$ meteor publish --release 0.9.3-rc5
downloading meteor-tool at version 1.0.31-rc5 ... done
Reading package...
publishing the package
Figuring out the best package versions to use. This may take a moment. its just stalling |
Then still no solution till now Mr. Raix? Good luck then 👍 |
And now it finally ended... $ meteor publish --release 0.9.3-rc5
downloading meteor-tool at version 1.0.31-rc5 ... done
Reading package...
publishing the package
Figuring out the best package versions to use. This may take a moment.
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
Abort trap: 6 |
Is this a duplicate of #2585? |
Note: I've tried removing meteor and reinstalling and publishing - but makes no difference |
@raix, yeah, it looks like that issue exactly... nothing for ages and then eventually memory timeout. just posted some more info on that thread now, but as mentioned i could publish with meteor from devel. |
@ekatek any hint on where to debug/ what to test |
Hah. I have been debuging this all afternoon. Good news, is that I can replicate it and I know why it works from checkout -- it seems to be choking on core packages specifically, and from checkout, there is only one version of those packages, so there is nothing to choke on. Well, that's 'good', but it is not really good in any meaningful way. Bad news, is that as far as I can tell, the constraint solver chokes on situations that don't seem to have much in common. For example, a package using mongo-livedata & templating alone is stuck. A package using mongo-livedata, templating and accounts-base is fine. So, I am going to keep debugging -- probably it will be something trivial in some bizarre manner. Not abandoning you, or this issue -- looking at actively in hopes of fixing in 0.9.3 -- but no solutions from me yet. |
Thanks @ekatek, from the symptoms it feels like the constraint solver goes into recursive infinity, eg. Trying to solve the same constraints over and over again. |
Nope -- I got a super clean reproduction, unfortunately. :/ meteor create --package foobar; and then add templating & mongo-livedata. It totally is the constraint solver going in for a loop, but I am not sure why (yet). Going to hunt the bastard bug down, I promise! Just wanted to keep you all in the loop. :) |
We tracked this problem down, and it requires some extra constraint solver changes. We don't feel comfortable putting those changes in 0.9.3 at the 11th hour (especially since it is more like '11:45' right now. :p), but they will almost certainly go into 0.9.4. Thank you so much for your patience -- stay tuned for a fix. |
(And the workaround for now is to publish from a checkout.) |
@ekatek Just an update - I've just updated to 0.9.3 and managed to publish one package, but the next package fails / stalls $ meteor publish
Reading package...
publishing the package
Figuring out the best package versions to use. This may take a moment. Theres a pattern since the first publish changes things causing the next packages to hang. |
Try it now! We think that we might have fixed the problem server-side. |
Looks good @ekatek, I've just tested by publishing 3 packages - I'm closing this :) |
Hi I'm trying to publish my packages but I cant..
and:
I've tried
meteor logout
andmeteor login
- this work fine (thought I might refresh tokens, but did nothing)I'm not sure what went wrong - I've changed nothing in the package.js as far as I can tell.
I'm not sure how I should make a reproduction of this - the process is stalling on all the packages I've tried to
meteor publish
cc: @ekatek
The text was updated successfully, but these errors were encountered: