WildMeOrg
Selecting multiple locations on rematch causes matching error
Expected behavior Selecting a top-level region (such as Pacific Ocean) in the "start a match" or "start another match" workflow results returns match candidates in all selected locations.
Current behavior Selecting a top-level region (such as Pacific Ocean) in the "start a match" or "start another match" workflow results returns "error initiating IA job" on match results page. However, leaving the default encounter location selected displays match candidates.
This has been reported and replicated in Flukebook and Sharkbook.
This has not yet been tested with selecting multiple location IDs on a bulk import.
Community link https://community.wildme.org/t/error-initiating-ia-job-flukebook/4650/5 https://community.wildme.org/t/access-denied-permissions/4523 https://community.wildme.org/t/sharkbook-matching-against-global-database-timing-out/4694
summary from slack discussion: this appears to be a bug in datanucleus that single-character location ids cause an exception in the query-building code, around the special {...} literal notation. workaround is to keep at the update of location ids to hopefully eliminate such ids.
long-term solution: there does not appear to be a fix in dn5.x, and dn6.x requires tomcat11 (see also PR932) and thus major overhaul. we could possibly rework the query itself, but the current implementation was the result of another performance improvement. notably: this will go away when 10.6 goes live, as it is part of querySet creation, so long-term may solve itself.
