"Map of challenge caches" filtered to only show fulfilled challenges show some unfulfilled too.

Question

Page:

http://project-gc.com/Tools/Challenges?map=create&country=Sweden&region=Sk%C3%A5ne&cachename=&archived=on&excludeNotFulfilled=on&show=has

Unfulfilled challenges that shows has this icon for example GC4367K.
The icon name correctly indicates type=Unknown Cache&color=green&checkerExists

But if i understand it right, when you chose to exclude "Not fulfilled" the cache shouldn't been shown at all as the tag "checkerSuccess" isn't present.

I have also one more hit that seems odd on GC2HZER that we have fulfilled and logged.

Could it be that challenges with checkers that are somewhat more demanding on resources gives an ambiguous reply when building the webpage?

I have tried this on Windows10 with Firefox, Chrome, IE and Edge all with the same result.

Answer 1

That blue circle with a question mark indicates that the fulfilment status is unknown, therefore caches with that icon will not be excluded by either Fulfilled or Unfulfilled filters (neither will challenges without checkers). This fulfilment is according to the checker, so these caches don't appear to have had the checker run for your account. You can go into the individual checkers and run them (using the links available on the challenge map) or, if you're a paying member of PGC, they will run automatically at some stage in the future.

Fulfilled challenges are shown with  and unfulfilled ones with .

Comments

When I run the individual checkers they always show the correct result.

That indicates to me that it's only the background task that store my results for each checker and if I run it manually the result isn't stored for further use.

It would be nice to have the filter "excludeUnknownFulfilled".

I'll just sit back and wait for the background task to have the specific checkers executed for my account ;)

Answer 2

GC2HZER is a special case. It is an old checker written in native PHP.
It is not integrated in the autorun system and will never have a pass or fail there but always a blue questionmark.
There are som other the most common is the 360 degrees challenges.
They will likely not be rewritten sin the old php checkers has access to not found cacher and can show caches to log to complete it. The new LUA checker has no access to not found cache