[Bug] Duplicate regions / unable to unprepare

[rchampine]

In the course of final revisions for Des Moines, Iowa | 1957 | Vol. 1, four regions of page 84 were somehow created where there should only be two. It now has duplicated regions. The "unprepare" function is not working for this page — it appears to get stuck in the loading phase.

[mradamcox]

Ok, I just went in and fixed these particular items. Can't investigate further now, so I'll leave this ticket open until I can.

[rchampine]

Thanks!

[mradamcox]

Seems like this was a one-off issue, closing now.

[mradamcox]

@mhpob encountered this again today on two separate occasions. It really seems like a split session just gets inadvertedly submitted twice, and there is nothing stopping it from running a second time and generating duplicate output.

I was able to replicate a similar issue like this:

1. Split a document and click submit
2. Use the back button to go back to the split interface
3. Submit the split again

This results in extra regions being created and attached to the already-in-progress session. Pretty sloppy, really need to re-examine this workflow from the backend... much more focus has been put on the front-end lock implementation, hiding links, showing "session in progress", and it's clear the backend needs some work in this regard now.

Resources to cleanup while fixing this:

• https://oldinsurancemaps.net/document/81117
• https://oldinsurancemaps.net/document/69168
• https://oldinsurancemaps.net/document/61166

[jpole1]

Just encountered this same bug.

• https://oldinsurancemaps.net/document/82183

Prepared this page, then too quickly clicked in to prepare it again. Once both instances of the page were created, I'm unable to unprepare it on my own.

[jpole1]

I think a similar issue is happening here -- https://oldinsurancemaps.net/map/sanborn03376_011. I just prepared page 0, but there's a weirdly labeled version of the snipped section of Page 0 that's already prepared, and there's still a Page 0 saying unprepared.

EDIT -- appears that was just a lagging loading issue. Please disregard.