AtlasOfLivingAustralia/biocache-hubs

Verify annotation not working

Closed this issue · 5 comments

nickdos commented

There seem to be a few issues with the Verify annotation function.

  • The modal div reports Record is marked as geospatially suspect, taxonomically suspect when the only annotation is marked as other issue. See screenshot:

image

  • Also note the user ID for the annotation (XXX issue flagged by ...) is empty above but is showing in the next screenshot (reported in a support ticket):

image

When viewing the same record I don't see the user name - https://biocache.ala.org.au/occurrences/72d3e802-5d4a-4fdd-a1b8-304868fd2413#userAnnotationsDiv nor do I see the verification reply, shown in the screenshot above.

  • Clicking the Confirm button does nothing. There are no JS errors but it has no effect at all. Cancel button does work.

Another user reported when they tried it, the Confirm button did work but they then got a long error popup. See:

image

alexhuang091 commented

Hi Nick, do you have the link to the record in first issue, thanks ?

nickdos commented

https://biocache.ala.org.au/occurrences/4db7b1b8-ad78-42c5-a6ec-bae270d3a0f2

I tried again now and got an error:

image

image

I can also see Margaret's verification on the other record today but it was not showing yesterday. I wonder if the load balancer is to blame?

alexhuang091 commented

Hi Nick, for the second issue. Biocache-hubs calls biocache-service/ws/occurrence/uid/assertions for all assertions and it sometimes get this (https://biocache.ala.org.au/ws/occurrences/3fb03272-09f6-48df-8bc5-469ffdf89d32/assertions). This wrong data is the reason UI breaks.

The email field looks wrong, but more importantly the uuid_field is wrong
截屏2021-03-19 下午3 27 53

However, when I debug locally with local biocache-hubs and biocache-services (this connects to production database), I can't reproduce this issue. The assertions returned are always correct so UI always good.

so

  • it has something to do with load balancer, at lease there's 1 machine returning correct result and the other not.
  • where the wrong result comes
nickdos commented

Thanks @alexhuang091 - I'm seeing the same output just now. I'll create an issue in biocache-service for this.
Done - AtlasOfLivingAustralia/biocache-service#568

nickdos commented

Closing as we determined that one of the load balancers was causing this issue.