Issues - relevance/log_buddy

relevance / log_buddy

Description:

logbuddy is your friendly little log buddy by your side

Sort by: Priority | Votes | Last Updated

Loading…

2.

0 votes

fix
x

still possible to get nil errors due to timing issues
1 comment Created 6 months ago by relevance

Title

Body
You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil.split /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.9/lib/log_buddy/utils.rb:25:in `parse_args’ /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.9/lib/log_buddy/mixin.rb:18:in `d’
or cancel
```
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.split
/Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.9/lib/log_buddy/utils.rb:25:in `parse_args&rsquo;
/Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.9/lib/log_buddy/mixin.rb:18:in `d&rsquo;
```
Comments
relevance Sun May 17 07:05:27 -0700 2009 | link
still possible to get nil errors due to timing issues

1) UsersController - requires login on signup Failure/Error: Unable to find matching line from backtrace You have a nil object when you didn’t expect it! You might have expected an instance of Array. The error occurred while evaluating nil.split # /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy- 0.4.10/lib/log_buddy/utils.rb:25:in `parse_args’ # /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.10/lib/log_buddy/mixin.rb:18:in `d’ # examples/controllers/users_controller_example.rb:15 # examples/controllers/users_controller_example.rb:13 # examples/controllers/users_controller_example.rb:51
Comment
**still possible to get nil errors due to timing issues** 1) UsersController - requires login on signup Failure/Error: Unable to find matching line from backtrace You have a nil object when you didn’t expect it! You might have expected an instance of Array. The error occurred while evaluating nil.split # /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy- 0.4.10/lib/log_buddy/utils.rb:25:in `parse_args’ # /Users/rsanheim/.gem/ruby/1.8/gems/relevance-log_buddy-0.4.10/lib/log_buddy/mixin.rb:18:in `d’ # examples/controllers/users_controller_example.rb:15 # examples/controllers/users_controller_example.rb:13 # examples/controllers/users_controller_example.rb:51
or cancel
Parsed with GitHub Flavored Markdown
3.

0 votes

feature
x

Should init itself by default on require
0 comments Created 6 months ago by relevance

Title

Body
[original LH ticket](http://relevance.lighthouseapp.com/projects/19074/tickets/5) This ticket has 0 attachment(s).
or cancel

original LH ticket

This ticket has 0 attachment(s).

Comments

Parsed with GitHub Flavored Markdown
4.

0 votes

LogBuddy clobbers rails script/generate when running Ruby 1.9
0 comments Created 17 days ago by rubyredrick

Title

Body
WIth logbuddy required in the environment, and when running Ruby 1.9.1 $ script/generate model foo undefined method `exists' for #<ActiveSupport::BufferedLogger:0x0000010221ea38> The Object#logger method added by LogBuddy is confusing the Rails generate command which uses logger as the name of the object which interacts with the project's files, not the normal use of the word, but it is what it is. I ran this under the debugger today, and confirmed that the generator is somehow getting the looger from logbuddy.
or cancel

WIth logbuddy required in the environment, and when running Ruby 1.9.1

$ script/generate model foo undefined method `exists' for #<ActiveSupport::BufferedLogger:0x0000010221ea38>

The Object#logger method added by LogBuddy is confusing the Rails generate command which uses logger as the name of the object which interacts with the project's files, not the normal use of the word, but it is what it is.

I ran this under the debugger today, and confirmed that the generator is somehow getting the looger from logbuddy.

Comments

Parsed with GitHub Flavored Markdown

Labels

▾
feature
▾
fix

fixx still possible to get nil errors due to timing issues

Comments

featurex Should init itself by default on require

Comments

LogBuddy clobbers rails script/generate when running Ruby 1.9

Comments

fix
x

still possible to get nil errors due to timing issues

feature
x

Should init itself by default on require