steve8x8 / geotoad

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

Crash when searching by waypoint-id #251

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. run geotoad.rb --cacheType=traditional --difficultyMax=5 --difficultyMin=0 
--distanceMax=15 --format=gpx --foundDateExclude=0 --foundDateInclude=99999 
--output='/home/user/Desktop/' --queryType=wid GCXXXX

Program crashed with the following output:

/usr/share/geotoad/lib/search.rb:498:in `getWidSearchResult': undefined method 
`gsub' for nil:NilClass (NoMethodError)
    from /usr/share/geotoad/lib/search.rb:381:in `getResults'
    from /usr/share/geotoad/geotoad.rb:309:in `block in downloadGeocacheList'
    from /usr/share/geotoad/geotoad.rb:281:in `each'
    from /usr/share/geotoad/geotoad.rb:281:in `downloadGeocacheList'
    from /usr/share/geotoad/geotoad.rb:854:in `<main>'

What version of the product are you using? On what operating system?
GeoToad 3.17.1 Arch Linux kernel v3.4.4

Original issue reported on code.google.com by julianke...@googlemail.com on 15 Jul 2012 at 4:08

GoogleCodeExporter commented 9 years ago
It might have been essential to know which WID caused the problem, and also to 
have some debug output (use -v option, or press "v" in TUI).
I suppose you didn't want to actually check out the archived cache GCXXXX in 
New Jersey, did you?

Original comment by Steve8x8 on 23 Jul 2012 at 9:00

GoogleCodeExporter commented 9 years ago
I just reproduced the error with GC3QJ2H. No I didn't mean the actual GCXXXX ;)

Original comment by julianke...@googlemail.com on 24 Jul 2012 at 5:48

GoogleCodeExporter commented 9 years ago
I just noticed the crash I thought to have reproduced was because of having 
used the wrong path in --output. If you find the bug anyway It's good, else 
close the issue, waypoint search works for me it seems.

Original comment by julianke...@googlemail.com on 24 Jul 2012 at 6:05

GoogleCodeExporter commented 9 years ago
Can you try to reproduce the bug, and send verbose output?
I seem to be unable to find the culprit - a bad target directory should be 
effective in output.rb, not search.rb, so this sounds like a red herring to 
me...

Original comment by Steve8x8 on 4 Sep 2012 at 8:23

GoogleCodeExporter commented 9 years ago
No additional info for months, therefore no way to reproduce this bug. Closing 
as WontFix.

Original comment by Steve8x8 on 30 Dec 2012 at 3:02