[Bug]: Server crashes when selecting a specific layer that populates on different zoom levels

[ileoyu]

What happened? What did you expect to happen?

Repro steps:

1. Ensure Capital Project toggle is turned on
2. Turn on filter by location and set it to Community District
3. Navigate to around where Brooklyn 13 is
4. Zoom in and out till you see that specific spot from attached screenshot
5. Select it

Expected: That specific area should not show on any zoom level

Actual: The affected area shows up on random zoom levels and when selected, server crashes.

What browsers are you seeing the problem on?

No response

Which operating system are you using?

None

[ileoyu]

If unable to replicate from map, here's URL -

https://staging-capitalplanning.nycplanningdigital.com/capital-projects/801/CONEYTOPO?districtType=cd&cbbrAgencyCategoryResponseIds=5%2C1&cbbrPolicyAreaId=2&cpPage=2

not sure what "CONEYTOPO" is

[TangoYankee]

@ileoyu Thank you for sharing the URL in the screenshot (and posting the comment just now). I noticed the referenced capital project is 801 CONEYTOPO. This project existed in the previous version of the Capital Project data. As of 3:48 this afternoon, we updated the capital projects in staging with the next version of data. 801 CONEYTOPO does not exist in this update. (Production still has the previous version. The project is visible there: https://capitalprojects.nycplanningdigital.com/801/CONEYTOPO)

My hypothesis is that the ghosts of this project are haunting the application. The ghosts would be:

• The URL pointing to the project existing in browser history
• The tile of the project existing in the cache and still being shown on the map

[TangoYankee]

@ileoyu Are you still seeing the behavior in the map? It should have gone away as the cache expired.

Note: we do expect the link to the project to cause an error; it no longer exists in the data. The project should no longer be visible on the map (as described in the original bug)