search

steve8x8 / geotoad

Geocaching query tool written in Ruby
https://buymeacoffee.com/steve8x8
Other
28 stars 8 forks source link

./geotoad.rb:960: undefined method `debug' for main:Object (NoMethodError) #276

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. execute geotoad with CLI command. Minimal output I found resulting in the 
error was: "./geotoad.rb Amsterdam"

What is the expected output? What do you see instead?
Expected is that collection of data from GeoCaching.com will start, however 
error on line 960 is shown and no collection of data is started:
(===) GeoToad 3.16.8 (x86_64-linux-1.8.7)
( - ) Report bugs or suggestions at http://code.google.com/p/geotoad/issues/
( - ) Please include verbose output (-v) without passwords in the bug report.

D: No user/password option given, loading from config.
( o ) Loading configuration from /home/roland/.geotoad/config.yaml
D: Internally using distance 10 miles.
./geotoad.rb:960: undefined method `debug' for main:Object (NoMethodError)

What version of the product are you using? On what operating system?
3.16.8 on CentOS release 5.9 (Final)

Reverting back to 3.16.7 solves the issue.

Original issue reported on code.google.com by RBorlet on 28 Jun 2013 at 12:01

GoogleCodeExporter commented 9 years ago 
This probably is a result of fixing:
"History logging to local disk (for futurewarning: peer certificate won't be 
verified in this SSL session survey purposes)"

Original comment by RBorlet on 28 Jun 2013 at 12:16

GoogleCodeExporter commented 9 years ago 
It is :( Obviously QA has done a bad job (for unknown reasons - brains on 
holidays is the most probable explanation).
Workaround: Disable history using the -H flag.
Patch is being worked on, there'll be a 3.16.9 soon. Priority elevated.
Sincere apologies...

Original comment by Steve8x8 on 1 Jul 2013 at 8:28

GoogleCodeExporter commented 9 years ago 
The SSL warning should disappear when switching to Ruby 1.9, btw.
The issue is supposed to be fixed by the latest release - at least I didn't see 
any complaints yet... closing

Original comment by Steve8x8 on 10 Jul 2013 at 7:39