
I forgot to mention: I can reproduce this on Mac and Windows.
--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/IOJ6Ifu2Dqo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/8ef5ec7f-e557-4940-973a-f4524cf37632n%40googlegroups.com.
Hi
I recently noticed that a dive I logged where I selected a dive site I've been to before created a second dive site with the same name in the dive site overview. Also, the number of dives shown for this dive site is wrong. It shows 1 and 3 dives respectively, where it should just show 1 dive site with 2 dives logged.
This seems to be the only dive site with this problem.
Am I misunderstanding the overview? Is this a bug?


I suspect the issue is in how the location dropdown selection is committed. It looks like the UI and backend state can get out of sync: I select an existing site, but the UI may still be in “create new dive site” mode. When saving, the code then follows the “create new site” path, but with data copied from the currently selected backend dive site, producing a duplicate.
In my XML export, the duplicate sites have UUIDs that differ by exactly 1. That looks like UUID collision avoidance logic kicking in, which strongly suggests these entries are true byte-level duplicates (same site data, different UUID).