On Monday, March 16, 2015 at 4:06:16 PM UTC-7, Peter Washburn wrote:
>
> I'm experiencing a similar issue with postgres(pg 0.17.1). Here's my 
> backtrace:
>
> 2.1.3 :003 >   DB
>
> #<Sequel::Postgres::Database: {:adapter=>"postgres", :host=>"athenadb", 
> :port=>5432, :encoding=>"utf8", :database=>"athena_dev", :user=>"postgres", 
> :password=>nil, :max_connections=>10, :loggers=>[#<Logger:0x007faf7b8f9670 
> @progname=nil, @level=0, 
> @default_formatter=#<Logger::Formatter:0x007faf7b8f95f8 
> @datetime_format=nil>, @formatter=nil, 
> @logdev=#<Logger::LogDevice:0x007faf7b8f9440 @shift_size=nil, 
> @shift_age=nil, @filename=nil, @dev=#<IO:<STDOUT>>, 
> @mutex=#<Logger::LogDevice::LogDeviceMutex:0x007faf7b8f93a0 @mon_owner=nil, 
> @mon_count=0, @mon_mutex=#<Mutex:0x007faf7b8f9350>>>>]}>
>
> 2.1.3 :004 > DB[:accounts]
>
> ArgumentError: wrong number of arguments (0 for 1..2)
>
> from 
> /Users/pwashburn/.rvm/gems/ruby-2.1.3/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:686:in
>  
> `to_hash'
>
> from 
> /Users/pwashburn/.rvm/gems/ruby-2.1.3/gems/awesome_print-1.6.1/lib/awesome_print/formatter.rb:67:in
>  
> `awesome_self'
>
It's fairly obvious the problem is in awesome_print.  It shouldn't be 
calling to_hash without arguments if to_hash requires an argument.

Thanks,
Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to