Failed to execute 'geddy auth' #279

Closed
Max-Might opened this Issue Dec 1, 2012 · 21 comments

Comments

Projects
None yet
7 participants
@Max-Might
Contributor

Max-Might commented Dec 1, 2012

> ../node/bin/node ../node/bin/geddy --version
0.6.17

I was reading the docs and decided to try the auth command in my new application.
Here is what happened:

> ../node/bin/node ../node/bin/geddy auth
This command will create/overwrite files in your app.
Do you wish to continue? (yes|no)
yes
Installing geddy-passport@0.0.x passport@0.1.x passport-local@0.1.x passport-facebook@0.1.x passport-twitter@0.1.x passport-yammer@0.1.x...
jake aborted.
Error: Process exited with error.
    at fail (/home/max/Projects/node/lib/node_modules/geddy/node_modules/jake/lib/api.js:221:18)
(See full trace by running task with --trace)

This message is not that helpful, what can I do to get more info about this error?

@Techwraith

This comment has been minimized.

Show comment Hide comment
@Techwraith

Techwraith Dec 1, 2012

Contributor

Yeah, this is a really unhelpful error message. We're working no making those nicer.

@mde Do you have any idea why this might fail?

Contributor

Techwraith commented Dec 1, 2012

Yeah, this is a really unhelpful error message. We're working no making those nicer.

@mde Do you have any idea why this might fail?

@mde

This comment has been minimized.

Show comment Hide comment
@mde

mde Dec 2, 2012

Contributor

This is a real problem for all the CLI commands that offload to Jake. We need a replacement error message, and a way to flip on verbose errors. There are a number of reasons this could fail -- flaky network access, insufficient perms to write in the directory, etc. No way to know until we get a decent error message.

I've opened a ticket for this: mde#281

Meanwhile, what OS and version of Node are you on?

Contributor

mde commented Dec 2, 2012

This is a real problem for all the CLI commands that offload to Jake. We need a replacement error message, and a way to flip on verbose errors. There are a number of reasons this could fail -- flaky network access, insufficient perms to write in the directory, etc. No way to know until we get a decent error message.

I've opened a ticket for this: mde#281

Meanwhile, what OS and version of Node are you on?

@MiguelMadero

This comment has been minimized.

Show comment Hide comment
@MiguelMadero

MiguelMadero Dec 2, 2012

Contributor

Hace you tried running It with -d. I remember changing it so it adds
the --trace flag in Jake, although this might've changed when we switched
to use jake inproc.

You could also try debugging the command, not ideal but a possible
workaround

On Sunday, December 2, 2012, Matthew Eernisse wrote:

This is a real problem for all the CLI commands that offload to Jake. We
need a replacement error message, and a way to flip on verbose errors.
There are a number of reasons this could fail -- flaky network access,
insufficient perms to write in the directory, etc. No way to know until we
get a decent error message.

I've opened a ticket for this: #281mde#281

Meanwhile, what OS and version of Node are you on?


Reply to this email directly or view it on GitHubhttps://github.com/mde/geddy/issues/279#issuecomment-10926527.

Miguel

Contributor

MiguelMadero commented Dec 2, 2012

Hace you tried running It with -d. I remember changing it so it adds
the --trace flag in Jake, although this might've changed when we switched
to use jake inproc.

You could also try debugging the command, not ideal but a possible
workaround

On Sunday, December 2, 2012, Matthew Eernisse wrote:

This is a real problem for all the CLI commands that offload to Jake. We
need a replacement error message, and a way to flip on verbose errors.
There are a number of reasons this could fail -- flaky network access,
insufficient perms to write in the directory, etc. No way to know until we
get a decent error message.

I've opened a ticket for this: #281mde#281

Meanwhile, what OS and version of Node are you on?


Reply to this email directly or view it on GitHubhttps://github.com/mde/geddy/issues/279#issuecomment-10926527.

Miguel

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Dec 29, 2012

Hi, i've another trouble to execute 'geddy auth', it returns this error:

jake aborted.
TypeError: Object # has no method 'resume'
at new Interface (readline.js:58:9)
(See full trace by running task with --trace)

what is the matter?

carlol commented Dec 29, 2012

Hi, i've another trouble to execute 'geddy auth', it returns this error:

jake aborted.
TypeError: Object # has no method 'resume'
at new Interface (readline.js:58:9)
(See full trace by running task with --trace)

what is the matter?

@mde

This comment has been minimized.

Show comment Hide comment
@mde

mde Dec 30, 2012

Contributor

Try running it with the debug switch, so we can see exactly where it's breaking geddy auth -d -- I've never seen this error before. What version of Geddy, Node, and what operating system are you using?

Contributor

mde commented Dec 30, 2012

Try running it with the debug switch, so we can see exactly where it's breaking geddy auth -d -- I've never seen this error before. What version of Geddy, Node, and what operating system are you using?

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Dec 30, 2012

OS: Ubuntu 12.04
geddy -v: 0.6.18
geddy auth -d: (same error)

jake aborted.
TypeError: Object # has no method 'resume'
    at new Interface (readline.js:58:9)
(See full trace by running task with --trace)

I believe it's like it's not recognizing the command.

obviuosly I installed geddy by sudo npm install geddy -g

i've tried that on a default geddy app.

carlol commented Dec 30, 2012

OS: Ubuntu 12.04
geddy -v: 0.6.18
geddy auth -d: (same error)

jake aborted.
TypeError: Object # has no method 'resume'
    at new Interface (readline.js:58:9)
(See full trace by running task with --trace)

I believe it's like it's not recognizing the command.

obviuosly I installed geddy by sudo npm install geddy -g

i've tried that on a default geddy app.

@mde

This comment has been minimized.

Show comment Hide comment
@mde

mde Dec 30, 2012

Contributor

What version of Node? (node -v)

Contributor

mde commented Dec 30, 2012

What version of Node? (node -v)

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Dec 30, 2012

sorry:
node -v: v0.6.12

carlol commented Dec 30, 2012

sorry:
node -v: v0.6.12

@mde

This comment has been minimized.

Show comment Hide comment
@mde

mde Dec 30, 2012

Contributor

Ah, there's the problem. Ubuntu's package for Node is out of date. Update
to version 0.8, and things should work fine.

On Sun, Dec 30, 2012 at 1:45 PM, Carlo Luchessa notifications@github.comwrote:

sry:
node -v: v0.6.12


Reply to this email directly or view it on GitHubhttps://github.com/mde/geddy/issues/279#issuecomment-11769068.

Contributor

mde commented Dec 30, 2012

Ah, there's the problem. Ubuntu's package for Node is out of date. Update
to version 0.8, and things should work fine.

On Sun, Dec 30, 2012 at 1:45 PM, Carlo Luchessa notifications@github.comwrote:

sry:
node -v: v0.6.12


Reply to this email directly or view it on GitHubhttps://github.com/mde/geddy/issues/279#issuecomment-11769068.

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Dec 30, 2012

it's 11pm here so i'll try it tomorrow,
thank's a lot ;)

carlol commented Dec 30, 2012

it's 11pm here so i'll try it tomorrow,
thank's a lot ;)

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Dec 31, 2012

ok, it works with
node -v: v0.8.16

I followed this guide: http://bit.ly/TBA3TS to update node in Ubuntu 12.04.

carlol commented Dec 31, 2012

ok, it works with
node -v: v0.8.16

I followed this guide: http://bit.ly/TBA3TS to update node in Ubuntu 12.04.

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Jan 1, 2013

Contributor

Hey @carlol don't use that PPA, there's an official PPA to use, do the following to get it.

sudo apt-get remove nodejs nodejs-dev npm
sudo apt-add-repository -r ppa:richarvey/nodejs
sudo apt-get update
sudo apt-add-repository ppa:chris-lea/node.js # If you want the unstable branch, the ppa is `ppa:chris-lea/node.js-devel`
sudo apt-get update
sudo apt-get install nodejs nodejs-dev npm

Chris Lea provides a ton of update packages for a bunch of projects, if you need a PPA you should see if he has it first :D

Contributor

larzconwell commented Jan 1, 2013

Hey @carlol don't use that PPA, there's an official PPA to use, do the following to get it.

sudo apt-get remove nodejs nodejs-dev npm
sudo apt-add-repository -r ppa:richarvey/nodejs
sudo apt-get update
sudo apt-add-repository ppa:chris-lea/node.js # If you want the unstable branch, the ppa is `ppa:chris-lea/node.js-devel`
sudo apt-get update
sudo apt-get install nodejs nodejs-dev npm

Chris Lea provides a ton of update packages for a bunch of projects, if you need a PPA you should see if he has it first :D

@carlol

This comment has been minimized.

Show comment Hide comment
@carlol

carlol Jan 1, 2013

thank's a lot for the suggestion :)

carlol commented Jan 1, 2013

thank's a lot for the suggestion :)

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Jan 1, 2013

Contributor

You're welcome, glad we could help!

Contributor

larzconwell commented Jan 1, 2013

You're welcome, glad we could help!

@leckster27

This comment has been minimized.

Show comment Hide comment
@leckster27

leckster27 Apr 16, 2013

Hi, I'm having a similar problem while trying to install nodejs-dev and npm in order to get the the "geddy auth" command to work. I get the same error when I try to do "geddy auth".

I've installed node using the instructions given by @larzconwell and still get the broken package issue when trying to install nodejs-dev.

nodejs -v : v0.10.4
geddy -v : 0.7.20

~$ sudo apt-get install nodejs-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs-dev : Depends: nodejs (= 0.8.22-1chl1~oneiric1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Hi, I'm having a similar problem while trying to install nodejs-dev and npm in order to get the the "geddy auth" command to work. I get the same error when I try to do "geddy auth".

I've installed node using the instructions given by @larzconwell and still get the broken package issue when trying to install nodejs-dev.

nodejs -v : v0.10.4
geddy -v : 0.7.20

~$ sudo apt-get install nodejs-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs-dev : Depends: nodejs (= 0.8.22-1chl1~oneiric1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Apr 16, 2013

Contributor

Hi @leckster27 recently the PPA merged the npm, nodejs, and nodejs-dev packages. So instead of installing the PPAS dev package it installed the out of date one in apt.

Instead do this:

sudo apt-add-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs

The nodejs now includes npm and the development headers for native code.

Contributor

larzconwell commented Apr 16, 2013

Hi @leckster27 recently the PPA merged the npm, nodejs, and nodejs-dev packages. So instead of installing the PPAS dev package it installed the out of date one in apt.

Instead do this:

sudo apt-add-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs

The nodejs now includes npm and the development headers for native code.

@leckster27

This comment has been minimized.

Show comment Hide comment
@leckster27

leckster27 Apr 16, 2013

@larzconwell, I did the previous steps and still get an error when I try the geddy auth commmand.

~/myProject$ geddy auth

WARNING: This command will create/overwrite files in your app.
Do you wish to continue?(yes|no)
y
Installing geddy-passport@0.0.x
jake aborted.
ode_ko
ode_modules: "geddy-passport@0.0.x"
(See full trace by running task with --trace)

@larzconwell, I did the previous steps and still get an error when I try the geddy auth commmand.

~/myProject$ geddy auth

WARNING: This command will create/overwrite files in your app.
Do you wish to continue?(yes|no)
y
Installing geddy-passport@0.0.x
jake aborted.
ode_ko
ode_modules: "geddy-passport@0.0.x"
(See full trace by running task with --trace)

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Apr 16, 2013

Contributor

Oh! it uses NPM to install the packages and with the PPA installs you'll need to use sudo.

Let me know how that works for you.

Edit: Even with local installs for some reason I noticed you have to use sudo for some reason..

Contributor

larzconwell commented Apr 16, 2013

Oh! it uses NPM to install the packages and with the PPA installs you'll need to use sudo.

Let me know how that works for you.

Edit: Even with local installs for some reason I noticed you have to use sudo for some reason..

@leckster27

This comment has been minimized.

Show comment Hide comment
@leckster27

leckster27 Apr 16, 2013

Wow... I feel a little sheepish, but that was the problem. Thanks for the quick help @larzconwell 👍

Wow... I feel a little sheepish, but that was the problem. Thanks for the quick help @larzconwell 👍

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Apr 17, 2013

Contributor

Awesome glad it's working for you!

Contributor

larzconwell commented Apr 17, 2013

Awesome glad it's working for you!

@larzconwell

This comment has been minimized.

Show comment Hide comment
@larzconwell

larzconwell Jun 13, 2013

Contributor

Closing since the core issue hasn't been touched in 6 months, seems to not be a problem anymore. Plus the issue #281 for the error handling.

Contributor

larzconwell commented Jun 13, 2013

Closing since the core issue hasn't been touched in 6 months, seems to not be a problem anymore. Plus the issue #281 for the error handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment