Hotspotter inspect error bug

Im not sure why I’m suddenly encountering so many issues on this platform. Jason let me know that the interface is getting upgraded to something new so hopefully these issues are a result of using this software, perhaps its not being maintained in the meantime.

When doing a hotspotter match, the hotspotter runs and works. Although when I click the inspect button I get an error.

https://tier1.dyn.wildme.io:5014/api/query/graph/match/thumb/?extern_reference=wlwkeaokuphmaixp&query_annot_uuid=e1b30f3a-a4aa-4145-80c7-18a609903d5c&database_annot_uuid=487c037f-4e55-4256-8f1f-b467b381386f&version=heatmask

{“status”: {“success”: false, “code”: 400, “message”: “Route error, Python Exception thrown: “””, “cache”: -1}, “response”: “Traceback (most recent call last):\n File “/wbia/wildbook-ia/wbia/control/controller_inject.py”, line 1198, in translated_call\n result = func(**kwargs)\n File “/wbia/wildbook-ia/wbia/web/apis_query.py”, line 1290, in query_chips_graph_match_thumb\n raise controller_inject.WebMatchThumbException(*args, message=message)\nwbia.control.controller_inject.WebMatchThumbException: \n”}Translate

Hi @evebohnett

Can you please send the link to the page that led you to the link above? I’ll take a look.

Thanks,
Jason

@jason It seems to be after using hotspotter on any image. After running hotspotter, then clicking on the inspect button does not lead to a side by side hotspot comparison of the orange hotspots. Instead it is an error message.

Here is an example hotspotter results page where you scroll over the result to see the inspect button:
https://www.whiskerbook.org/iaResults.jsp?taskId=4cc51256-0b85-4821-a6af-efac8b77f11e

I’m guessing that if you could run the hotspotter on any image in the Whiskerbook system… that you would find the inspect button in the results leads to that error.

Tagging @parham here. We’ll dig into this. Definitely some kind of bug. Thanks for letting us know!

This is the corresponding ID job and its raw compute result (https://tier1.dyn.wildme.io:5014/api/engine/job/result/?jobid=05c5dbca-1edd-45cc-85ec-6759aa9b4cb8&format=true). The dannot_extern_list indicates rendering errors when the job was completed, investigating.

1 Like

I think this is the same bug we’re seeing, which I reported, with link to examples, here: New error on "inspect" of match results processed 12/2 (less than 24hrs old)

Thanks for investigating @parham !

Maureen

We’re tracking as SAGE-473 and actively working on the fix.

Hi @evebohnett

This issue should be fixed for Whiskerbook, with future scans operating normally and past matches also backfilled with the Hotspotter inspect links now working. Can you please review and let us know if fixed?

@ACWadmin1 The fix is deployed for new matches, and we are currently regenerating the old match inspect link results.

Thanks,
Jason

1 Like

Great @jason That’s perfect. Yes, it’s fixed. It looks great and works when I check it!

1 Like