Internal server error when running `mrt release my-package`

[patreeceeo]

I have this package that I want to release to Atmosphere (https://github.com/pzatrick/meteor-bview) I followed the directions at https://atmospherejs.com/docs/publishing. Running mrt release meteor-bview, where meteor-bview is the relative path to my package folder, produces:

Adding tag and pushing repo
Error: Internal server error

And searching Atmosphere for my package yields nothing. Am I doing something wrong? Thanks!

[patreeceeo]

Note: running mrt release . from inside the directory gives the same result.

[tmeasday]

Hmm. For some reason I can't get to the logs right now but my guess would be the problem is you left a bunch of stuff out of smart.json (importantly the git URL). Not sure why it's throwing a 500, but I'd try fixing that and re publishing.

[patreeceeo]

Is there a way to find the versions of the packages I'm using in a meteor project? I want to use the same versions in this package.

[tmeasday]

You can look in smart.lock. Do you need to depend on all the packages for this package?

[Tarang]

Hi @pzatrick previously on atmosphere there were some error reports that get thrown. There were some sent last night which match the times when you tries to publish your project.

I'm a bit unsure of the underlying code @tmeasday, is it the same as on github? You can take over that tail-sh account and change the password if you wish. The logging is quite reliable & you get an email whenever there is a serious one (server side one).

this is what got thrown

Exception while invoking method 'publish' TypeError: Cannot read property '1' of null
    at Function._.mixin.parseAuthor (app/server/setup.js:19:35)
    at Meteor.methods.publish (app/server/methods.js:21:24)
    at null.<anonymous> (packages/filters/common.js:182)
    at maybeAuditArgumentChecks (packages/livedata/livedata_server.js:1406)
    at packages/livedata/livedata_server.js:580
    at _.extend.withValue (packages/meteor/dynamics_nodejs.js:35)
    at packages/livedata/livedata_server.js:579
    at _.extend.withValue (packages/meteor/dynamics_nodejs.js:35)
    at _.extend.protocol_handlers.method (packages/livedata/livedata_server.js:578)
    at packages/livedata/livedata_server.js:483

and

Exception while invoking method 'publish' Error: key parsley.js must not contain '.'
    at Object.Future.wait (/meteor/dev_bundles/0.3.32/lib/node_modules/fibers/future.js:323:16)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as insert] (packages/mongo-livedata/mongo_driver.js:561)
    at Meteor.Collection.(anonymous function) [as insert] (packages/mongo-livedata/collection.js:444)
    at Meteor.methods.publish (app/server/methods.js:12:10)
    at null.<anonymous> (packages/filters/common.js:182)
    at maybeAuditArgumentChecks (packages/livedata/livedata_server.js:1406)
    at packages/livedata/livedata_server.js:580
    at _.extend.withValue (packages/meteor/dynamics_nodejs.js:35)
    at packages/livedata/livedata_server.js:579
    - - - - -
    at Error (<anonymous>)
    at Function.checkKey (/meteor/containers/434fcb5d-322d-a4ea-3e38-4f613d58751a/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/node_modules. . . [truncated]

[patreeceeo]

I'm using the coffeescript and UI packages in a project (https://github.com/pzatrick/meteor-surveys), which is also using my "bview" package privately, and coffeescript and UI are the only dependencies of the "bview" package. The smart.lock in my project, however, does not list coffeescript or UI. I know UI is a standard app package, though I did install coffeescript using Meteorite. Is there a way to know what versions of coffeescript and UI I'm using in my project? Am I on the right track in thinking that I need to list these packages in the smart.json of my "bview" package?

[tmeasday]

Hey @pzatrick - coffeescript and UI are both core packages, so you don't need to include them in smart.json.

You are on the right track however :). In general, check package.js, see what you are use()-ing, and consider which packages aren't part of core.

[patreeceeo]

Success! Possibly just a matter of all the fields needing to be non-empty strings. Thanks for the help!