Bl4ckH4wkGER

Alright, here is the promised update Bugs that were fixed: PQs with attributes filters contain ANY is true instead of ALL is true PQ preview columns not sortable PQ preview distance column is empty Missing PQs when "uncheck the day of the week after the query runs" was checked Caches along a route PQs remain empty if "Found in the last 7 days" filter set Bugs that are still in the works: Caches along a route PQs return much less caches than anticipated (we now know what's causing this, we just need to do the work to fix it) PQs include Events even if Events are not selected (we're currently failing to reproduce this, so we may need additional screenshots etc @mbooda) PQs run immediately instead of on selected days (we're currently failing to reproduce this, so we may need additional screenshots etc @mbooda) Please continue to bring up new issues as you encounter them. Thank you for your patience as we address the remaining bugs.

Thanks that's very helpful. That's been brought up several times in this thread and is part of the larger sorting issues on the PQ preview. We should have a fix for that later today.

@mbooda Thanks for the report. Could you clarify with what types of PQs you're seeing this? PQs from a List PQs from the map PQs along a route standard PQ all the above By selected types, I assume you mean cache types. Again, we need more specifics of what you're trying to include and what is included instead. @ all Regarding the other bugs, we'll be releasing some fixes at the end of tomorrow's sprint, Tuesday November 2, at the end of the day pacific time. I will post again once the release is out.

I've merged the two duplicate threads.

@TommyGator Done, thanks for the offer

If you are experiencing any particular issues, it'd be great if you'd share them. That way we can either acknowledge them as known or help you and others by documenting new bugs and fixing them. Otherwise the tone of your message seems misplaced, especially because based on your last statement you don't know what has gone into this release up until this point - frankly, how would you. The original PQ code was ancient. Documentation for it was close to non-existent and so a lot of the work to get to this release was forensics, documenting, implementing, and then working with a test group of long term PQ users to verify whether what they were seeing matched the old expectations. Internal testing with HQ staff began in May, followed by a player-test group in June. The production release was in October. Pocket Queries offer a very extensive number of options, combinations, ways to create them, etc. The fact that across those 1000s of options, yes you read that right, we've only had ~10 bugs, I'd call that a win and a display of the hard work that has gone into QAing this. And to those who are saying "well, there shouldn't be any bugs", that's not how software development works no matter how solid your practices are and how many unit-tests you write.

@TommyGator thanks for the report. The issue is already captured in the list of bugs that is actively being worked on. You can find the full list by looking 3 posts above yours:

You may have a better chance of people reading and responding to your suggestion if you remove the formatting from your post. Currently it looks like this:

That is correct. @DaTechniker I just wanted to circle back and say that we re-ran the four missing queries for you that you had highlighted: The discussion at the time was correct, that ad hoc PQs weren't carried over into the new system because they were handled by a different query job. That was an oversight on our end. If anybody is still missing ad hoc queries, please feel free to re-run them. Any missing PQs would expire tomorrow, so you'd be close to re-running them anyway. We apologize for any inconveniences caused. Going forward, any newly scheduled ad-hoc PQs will run. @ all We're still working on the various bug fixes that were previously mentioned: Sorting columns on PQ preview refreshes the page but doesn't actually sort Distance column on PQ preview remains empty if PQ is relative to home coordinates Attribute filters return caches with EITHER attribute instead of BOTH attributes User route PQs don't contain all expected results User route PQs remain empty if "Found within 7 days" is checked I will circle back when we have fixes.

You are correct. Allow me to clarify The only logs that are limited to the past 5 years due to the new implementation are "logs posted by other players." You will always see your own cache logs, regardless of how old they are.

Thank you all for the reports over the weekend. I have filed bug reports for the following issues: Sorting columns on PQ preview refreshes the page but doesn't actually sort Distance column on PQ preview remains empty if PQ is relative to home coordinates Attribute filters return caches with EITHER attribute instead of BOTH attributes User route PQs don't contain all expected results User route PQs remain empty if "Found within 7 days" is checked This is a limitation of the new system that we won't be able to rectify. It results from Pocket Queries no longer running straight against the database but instead against a data cache. The latter contains the last 5 years of data (that's when it was implemented) and will continue to populate going forward. I understand that it may be inconvenient in your area, and apologize for the inconvenience. Overall, the number of caches that haven't been found in 5 years is very small. We hence consider this tradeoff as manageable, if it improves performance for all players at scale. Please take a moment to compare the bug reports from other players in this thread and your own. Unfortunately, it is missing crucial information. I'd be happy to help you once you provide some screenshots & the Pocket Query ID for troubleshooting.

Thanks for the additional reports. While it appears fixed for general seek/nearest searches it's indeed still broken for PQ previews. We will revisit the sorting issues on Monday.

This has been fixed.

We have now deployed fixes for the following bugs: Pocket query preview does not work properly, including sorting PQs only include regular Events, bot none of the other ones PQs that have the "Found in the last 7 days" filter checked remain empty Wrong order of <author> element makes import into Garmin MapSource fail New PQs for caches along a route don't run As you keep using PocketQueries over the weekend, please let us know if you run into any funky behavior. Happy geocaching

@t@bbywmn It's on the list and pending deployment. See the list at the end of my post from 1h ago here:

@DaTechniker Thank you for the follow-up and the additional detail. I will follow up with our engineers to check about the PQs that were scheduled with "uncheck the day of the week after the query runs" checked. I'll see whether we can either migrate missing data or even if not that we make sure that such queries run as expected going forward. For general context, with most PQs running once a week, we always had to pre-populate a whole week before making the release switch. While I expected some queries to get dropped in the process, I want to make sure that once the switchover week is done, we have things running as expect again once all PQs would naturally run in the new service "for their first real run" Thank you for your help!

@DaTechniker Thanks for the additional reports. We had an earlier report of missing CCE events by @baer2006. As part of that fix we also looked at all the other Event types and have confirmed that they will be included appropriately once the fix is live. Unfortunately, I have a hard time following your second write-up. If I understand you correctly, the PQs number 16 to 19 ran on October 17. They were available at one point and you downloaded them and imported them but now you're saying that they're no longer available, when they should be available for another 3 days. If those PQs were ones that were scheduled in advance and part of the nightly runs, then I agree that they should have been duplicated appropriately. If they were manual on-the-fly PQ runs, those may have not been duplicated appropriately as the other examples we re-ran for you. It's not scalable for us to track down individual PQs for individual players. Instead it's more effective if we can focus on larger patterns that effect all players. Hence I propose the following: Wait to re-run any PQs until I have shared all the bugs that have been fixed to make sure you get the most complete data. If the problem PQs were single-run PQs and may have gotten lost, please rerun them. If they still don't work properly, please let us know. If the problem PQs were scheduled PQs and will rerun on Monday, October 24, let's wait for them to rerun and again, please let me know if there are still issues with them. Bug list pending QA and hotfix: Pocket query preview does not work properly, including sorting PQs only include regular Events, bot none of the other ones PQs that have the "Found in the last 7 days" filter checked remain empty Wrong order of <author> element makes import into Garmin MapSource fail New PQs for caches along a route don't run Again, I will let you all know once those are deployed. Thank you for your patience.

Here is my original post where I acknowledged that it was seen and that a fix is in the works: Here is another post from me 3h ago that we are aiming to resolve it before the weekend:

Thanks for the additional detail @Gamma5. I've passed it on to the engineer who was working on a fix. @all Several of the other bugs are code complete and pending QA. We're hoping to hotfix them before the weekend. I will report back once they have been deployed.

This has been fixed.

Please let us know if you continue to see issues with this. Thanks for digging into that. I'll create a ticket to see that we can get this back into the expected order.

@mustakorppi Could you take that conversation offline, please? The partner API is only indirectly related to this PQ API release. All API partners were given notice of the PQ changes and will be given notice of any other updates around cache types when they happen. If you see issues with any partner applications, please direct that to them directly. Even if the API tells them one thing, they can always adjust the display text on the frontend. Anyway, this isn't the place to dive into the partner API documentation. Thank you for staying on-topic.

@Gamma5 Thank you for reporting this issue. I see no prior mention of this from you or anybody else in this thread. The issues described by DaTechniker you had added a "+1" to before was a different one and the one empty query he encountered may have well been a glitch of us manually rerunning things. Now that you've provided more details, including the exact setup of your query, we can better look into it. I will open a ticket to investigate. Thank you for your patience.

Hard to say what is the issue without comparing the exact PQ output that you got from the directly downloaded file vs your GSAK GPX export. The new PQ files are every so slightly different to the old versions because of different systems and data formats involved. It may be that Garmin needs to update MapSource to account for those small changes. You could help us by copying the two texts into a tool like https://www.diffchecker.com/ and share the differences here or reach out to me via PN so we can find a way for you to send me the two files. Thanks for the report. I have create a ticket with our engineers to make sure that all Event types are correctly covered by PQs as advertised in the setup menu (*includes: Geocaching HQ Block Party, Cache In Trash Out Event, Giga-Event Cache, Community Celebration Event, Geocaching HQ Celebration, Mega-Event Cache).

I’ll respond to this comment representative for the various comments of “just leave it as is, it shouldn’t be that hard”. I understand that the work and cost needed with maintaining a website and keeping it up and running may not be clear for everyone, so let me give a more tangible examples: Imagine you live on a couple acres of land with a nice 3000 square feet house. It’s pretty old but looks in decent shape. However, it’d really be time for a remodel because the electrical and plumbing are still from when the house was built 70+ years ago. You had three kids and plenty of space and bedrooms to raise them. All your kids have long moved out and so it’s only you and your partner left in the big house on the big property. Even though there are now only 2 people living in the house instead of 5 people, you still have to: Pay the same property tax, maybe even more because it goes up every year Pay the exterminator to keep things pest free Clean the gutters Maintain the yard Keep things heated and dry so there’s no moisture damage Make updates required by law because hypothetically all houses must have solar now Etc etc etc You can’t just say that you’re not gonna fix the leaky roof because it’s over Billy’s room and Billy moved out so it’s fine. If you do that, you actively risk larger damage to your assets and other parts of the house. Same with not doing the necessary updates to your electrical and plumbing. All it takes is one busted pipe and you're looking at a couple grand in damages. Overall the cost to stay where you are far outweighs the benefit of the large house now that the kids have moved out and their families only all come over all at once for birthdays and holidays. Now, many of you will probably say “well, I’d just downsize and move somewhere else”. Bingo, that’s exactly what Geocaching is doing with benchmarking. We’re moving out into a smaller and more modern house with fewer bedrooms. We understand that selling the house you built and raised your family in can be hard and is an emotional moment, one where you don’t want to hear the numbers. That said, sometimes these tough choices are necessary to make sure that the whole family will be fine years down the road because if you don’t, the debt accrued by staying where you are is just gonna weigh down everyone. I hope you get the picture.