error: Police not ok (under node 0.8) #14

Closed
mhart opened this Issue Jul 1, 2012 · 6 comments

Projects

None yet

2 participants

@mhart
mhart commented Jul 1, 2012
~ police --help
info:   Welcome to Police
info:   It worked if it ends with Police ok
path.existsSync is now called `fs.existsSync`.
error:  Police not ok

Is there any way to run it in debug mode or something? There's no indication as to what's actually gone wrong...

Owner

Sorry, there is no debug mode. I will fix it today.

mhart commented Jul 1, 2012

After fiddling with the source for a bit, it seems that it's throwing an Error parsing your JSON configuration file.

When I did police auth, it seemed to work:

~ police auth
info:   Welcome to Police
info:   It worked if it ends with Police ok
path.existsSync is now called `fs.existsSync`.
prompt: username: mhart
prompt: password: 
info:   Authenticated to github as mhart
info:   Police ok

But when I look at ~/.policeconf I can see that it's empty. Removing it and running auth again has no effect (it reappears empty)

Owner

Maybe you have wrong permissions on the config file?

mhart commented Jul 1, 2012

Don't think that's it.

~ rm ~/.policeconf 
~ police auth
info:   Welcome to Police
info:   It worked if it ends with Police ok
path.existsSync is now called `fs.existsSync`.
prompt: username: mhart
prompt: password: 
info:   Authenticated to github as mhart
info:   Police ok
~ ls -l ~/.policeconf 
-rw-------  1 michael  michael  0  1 Jul 19:21 /Users/michael/.policeconf
~ cat ~/.policeconf
~ police --help
info:   Welcome to Police
info:   It worked if it ends with Police ok
path.existsSync is now called `fs.existsSync`.
error:  Police not ok
Owner

Let me check it it's an issue with node 0.8. I just woke up, so I will most probably fix it after an hour or so

@pksunkara pksunkara closed this in 68d59c5 Jul 5, 2012
Owner

It was due to some issue in nconf, Fixed and released v0.3.0 fully compatible with node 0.8

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