In which Wildbook did the issue occur? ACW
What operating system were you using? Win 10
What web browser were you using? latest chrome
What is your role on the site? admin
I’m getting 400 Python errors when I click on the inspect button in match results for matches run after Jan/Feb 2021. Which forces me to re-run matches when I shouldn’t need to.
Then, after waiting for the new match results, I’ve gotten an “attempting to fetch results” in all cases this afternoon. Refreshing the page multiple times has not helped.
What did you expect to happen?
I thought this issue was fixed - per the January release notes:
" * WB-1252 No more 400 Python errors (IAResults inspect) on new-and-very-likely matches
So I expected to be able to “inspect” the match results and see the 2 images side by side with hotspotter patches on the matched areas.
I have tried to inspect a few dozen previously run match results and am getting the 400 Python error on every single one. Here’s another example:
And when I re-run matching, both yesterday and today, I get the “attempting to fetch results” message. Refreshing the page hasn’t helped.
I refreshed yesterday’s match results pages today, and finally saw the match results display.
Is there a server issue or something?
I’d appreciate any info. It’s getting very frustrating.
Hi, @ACWadmin1 !
I was unable to reproduce this issue just now when I checked, but I experienced the same thing earlier today on ACW.
When I had my same issue, I checked and saw that there were quite a few IA jobs in the queue; my best guess is that this is what was going on, as all of those jobs have been completed now and results are displaying just fine.
Apologies for whatever it was that caused this, but seems to be working okay now…
Regarding the 400 python errors, I’ll ask the IA folks again right now; I know someone was looking into it yesterday, but I’m not sure what the conclusion was.
Hi, @ACWadmin1 !
From our IA specialist:
These match results are from April and May 2021
After 90 days, the ID comparison renders are deleted in WBIA to save space
even the job is archived after 2 weeks
Basically, they are trying to look at old matching jobs and WBIA has deleted the cached results…
It also prevents the need to link to the backend WBIA instance and its URL
We’ve run into this in the past, it’s certainly expected behavior across all WB projects.
if they were to resubmit the ID job, everything would work.
So, that’s the workaround. I will create a ticket to improve the UI so that the user doesn’t expect one thing and see an error instead asap.
Hi @MarkF - that makes sense. Going forward I’ll take screenshots of the great match results we find so as not to lose them.
Hi @MarkF - I just got a 400 Python error on inspect for a match result run yesterday:
Match results page: Wildbook for Carnivores
Go to match result #8 and click on inspect. You’ll see what I mean. It’s a really GREAT match and I really want to get the hotspot inspect compare to use for demo purposes.
Thoughts? Do I need to re-run this encounter again?
I’m asking about that one currently.
In the meantime, the UI-to-block-users-from-seeing-the-python-errors is in the system as WB-1780.
Hi @MarkF - 2 more Python errors on match results that were run Aug 13/21 and are not results after #16.
Match results #8 & 10 are both throwing the 400 Python error. Hopefully these additional examples help?
Hi, @ACWadmin1 !
This from JP:
Hi @mark - okay, I understand now. the blowing out of the cache isn’t a strict ‘everything older than 90 days’, it’s a ‘whenever the cache is full-ish’, which makes sense. We’ll update our workflow with our users - upload & process through IA smaller batches so they can be ID’d more quickly before a new batch is uploaded.