-
Notifications
You must be signed in to change notification settings - Fork 24
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
Exception thrown when attempting to do anything further than select a board #1
Comments
hey @menge101, yeah exactly, you need to select a board before you can do anything. I'm adding some warnings instead of it getting crashed. |
Fixed in version 0.1.7. |
I had already chosen a board. |
Would it be you selected the wrong board id? It has ben working for me. |
I'll spend a few minutes digging into it this afternoon. |
Yeah, it looks like you made some significant changes from the version I pulled. I used to see something like: 0 - [58b05a92d551b52227bf045e] - Personal projects And I was executing So this should be closed now. It appears I do not have the authority to close it. |
I see, I actually have plan of making it work the-index-way since copy-pasting the IDs every time is so tedious. Thanks anyway for posting the issue. |
I get the following exception when attempting to list lists, or card list mine
/Users/nmenge/.rvm/gems/ruby-2.4.0/gems/3llo-0.1.5/lib/3llo/client.rb:23:in
'get': invalid id (RuntimeError) from /Users/nmenge/.rvm/gems/ruby-2.4.0/gems/3llo-0.1.5/lib/3llo.rb:77:in
list_lists'from /Users/nmenge/.rvm/gems/ruby-2.4.0/gems/3llo-0.1.5/bin/3llo:38:in
block in <top (required)>' from /Users/nmenge/.rvm/gems/ruby-2.4.0/gems/3llo-0.1.5/lib/3llo/interface.rb:9:in
print_frame'from /Users/nmenge/.rvm/gems/ruby-2.4.0/gems/3llo-0.1.5/bin/3llo:34:in
<top (required)>' from /Users/nmenge/.rvm/gems/ruby-2.4.0/bin/3llo:22:in
load'from /Users/nmenge/.rvm/gems/ruby-2.4.0/bin/3llo:22:in
<main>' from /Users/nmenge/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in
eval'from /Users/nmenge/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `
The text was updated successfully, but these errors were encountered: