Skip to content
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

Closed
raix opened this issue Sep 21, 2014 · 18 comments
Closed

Cannot publish new version of package #2656

raix opened this issue Sep 21, 2014 · 18 comments

Comments

@raix
Copy link
Contributor

raix commented Sep 21, 2014

Hi I'm trying to publish my packages but I cant..

~/dev/packages/grounddb on Meteor-0-9-1
$ 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)
^C

and:

$ 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.
^C
$ meteor --version
Meteor 0.9.2.2

I've tried meteor logout and meteor 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

@raix
Copy link
Contributor Author

raix commented Sep 21, 2014

$ 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

@raix raix closed this as completed Sep 21, 2014
@raix
Copy link
Contributor Author

raix commented Sep 22, 2014

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?
Btw. Figuring out the best package versions to use. This may take a moment. - its not a moment, more like forever,

Thanks

@raix raix reopened this Sep 22, 2014
@ekatek
Copy link

ekatek commented Sep 22, 2014

What does it look like with 0.9.3-rc5? (We changed some bugs&output, might
be helpful)
On Sep 21, 2014 10:33 PM, "Morten N.O. Nørgaard Henriksen" <
notifications@github.com> wrote:

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 https://github.com/ekatek Any hints on where to investigate the
reason for the issue?
Btw. Figuring out the best package versions to use. This may take a
moment. - its not a moment, more like forever,

Thanks


Reply to this email directly or view it on GitHub
#2656 (comment).

@raix
Copy link
Contributor Author

raix commented Sep 22, 2014

$ 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

@radiegtya
Copy link

Then still no solution till now Mr. Raix? Good luck then 👍

@raix
Copy link
Contributor Author

raix commented Sep 22, 2014

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

@raix
Copy link
Contributor Author

raix commented Sep 22, 2014

Is this a duplicate of #2585?

@raix
Copy link
Contributor Author

raix commented Sep 22, 2014

Note: I've tried removing meteor and reinstalling and publishing - but makes no difference

@gadicc
Copy link
Contributor

gadicc commented Sep 22, 2014

@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.

@raix
Copy link
Contributor Author

raix commented Sep 23, 2014

@ekatek any hint on where to debug/ what to test

@ekatek
Copy link

ekatek commented Sep 23, 2014

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.

@raix
Copy link
Contributor Author

raix commented Sep 23, 2014

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.
Could it be an issue between versionfrom and meteor-platform package, or interferens from packages in $PACKAGE_DIR?

@ekatek
Copy link

ekatek commented Sep 23, 2014

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. :)

@ekatek
Copy link

ekatek commented Sep 25, 2014

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.

@avital
Copy link
Contributor

avital commented Sep 25, 2014

(And the workaround for now is to publish from a checkout.)

@raix
Copy link
Contributor Author

raix commented Sep 26, 2014

@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.

@ekatek
Copy link

ekatek commented Oct 1, 2014

Try it now! We think that we might have fixed the problem server-side.

@raix
Copy link
Contributor Author

raix commented Oct 2, 2014

Looks good @ekatek, I've just tested by publishing 3 packages - I'm closing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants