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

Fails with exception on first run #1

Open
atombender opened this issue Feb 26, 2013 · 1 comment
Open

Fails with exception on first run #1

atombender opened this issue Feb 26, 2013 · 1 comment
Labels

Comments

@atombender
Copy link

After installing the gem for the first time:

# gem install semaphore-status
Successfully installed semaphore-status-0.0.2
1 gem installed
# sst myproject
Please enter authentication token for your Semaphore account:
/usr/local/opt/rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/semaphore-status-0.0.2/bin/sst:79:in `gets': No such file or directory - myproject (Errno::ENOENT)
  from /usr/local/opt/rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/semaphore-status-0.0.2/bin/sst:79:in `gets'
  from /usr/local/opt/rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/semaphore-status-0.0.2/bin/sst:79:in `<top (required)>'
  from /usr/local/opt/rbenv/versions/1.9.3-p385/bin/sst:23:in `load'
  from /usr/local/opt/rbenv/versions/1.9.3-p385/bin/sst:23:in `<main>'

If I run it without any arguments it asks me for a token.

@rastasheep
Copy link
Contributor

Hi,

First time you run semaphore-status, you must provide your api authentication token, best way to do that is to run sst without arguments.

After that you can use semaphore status without providing authentication token again.

Authentication process with arguments will be fixed in next version, thanks for submitting issue,

Aleksandar.

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

No branches or pull requests

2 participants