Project-GC Q&A - Recent questions tagged issues

Rework of My Issues needed?

Mon, 15 Jun 2015 06:56:55 +0000

I have got to the stage of ignoring the My Issues section of Challenge Checkers. Every time I test a tag with the specified user it works fine. Every single time.

I currently have 13 Issues in my account, have checked three and frankly, can't be bothered checking the rest. They will all be fine.

Is there a fault with the auto qualifying system that occasionally throws erros that get flagged into my issues? I have left the issues there in case you need them to help track down the bug.

The concept is great, but the false positive rate is too high.

thanks,

Tom (geonick: the Seagnoid)

My Issues shows problems after last weekend outage

Fri, 27 Mar 2015 17:43:31 +0000

Page with challenge checkers/tags shows scripts/tags that failed (mostly) during last weekend outage (mostly bookmarks). When I run them by hand, it works fine, but I don't want to run them for all the failed users (the list is quite long).

Can you please consider some global rerun of failed scripts? I guess you would help more people who can be frustrated with the red color of the title. :)

I guess there is some automatic re-run when tag/script is changed (if not, it would be also usefult, but it is different topic).

"My issues" shows tag/script with no issues...

Mon, 02 Feb 2015 17:18:32 +0000

I don't know if it is a bug or not, but my script 733 / tag 5932 continously shows issues

I checked all of the below, users are premium users, ok is boolean, log and html are false or string, users have more than 0 finds and none of the below mentioned fields are used in the script. I am confused.

Coordinates can be false, common when a non premium member gets data for a premium geocache. You must handle this when calculating distance for example. Note that the premium status of the one running the script is what counts, therefore this can be hard to reproduce.
Invalid returns; ok must be a boolean, while log and html must be of type string or false.
The user has 0 finds and the script doesn't handle it correctly, or an effect of it.
The fields last_publish_date and last_archive_date can be false, for different reasons.
The fields region, county and elevation can temporary be NULL (nil in LUA). Since we do not get this data from Geocaching.com we calculate it afterwards. We advice treating these as none finds until they get their data.

I tried with user "huntersam" who was shown having issues. The checker showed a green "Success", using my user name it shows "red". No errors, whatsoever.

Thanks for your time.

Hampf