WildMeOrg / Wildbook

Wild Me's first product, Wildbook supports researchers by allowing collaboration across the globe and automation of photo ID matching
https://www.wildme.org/wildbook.html
GNU General Public License v2.0
101 stars 61 forks source link

DENYing an individual merge does not to seem to actually change the state of merge to denied #448

Open naknomum opened 4 months ago

naknomum commented 4 months ago

message in tomcat log seems to indicate success:

wildbook_1        | ==> In ScheduledIndividualMergeUpdate servlet!
wildbook_1        | Have all required info...
wildbook_1        | Merge real? 2a0364ba-57bc-436a-be6b-3c07ba63dc2b
wildbook_1        | user is participant? true
wildbook_1        | Set ScheduledIndividual merge 2a0364ba-57bc-436a-be6b-3c07ba63dc2b to DENIED for user erin3.

and yet state of said merge seems to be contrary to this:

out.println(sim.getId());
out.println(sim.getParticipantUsernames());
out.println(sim.getUsernameThatDeniedMerge());
out.println(sim.deniedByUser("erin3"));

2a0364ba-57bc-436a-be6b-3c07ba63dc2b
[erin4, erin3]
null
false
Paul-Kalil commented 4 months ago

Hello Jon, we have been telling our users to avoid requesting merges via the system because of this issue. We support getting this fixed asap. Thanks. Paul