Alright, I found the culprit.
Upload code is checking for duplicate titles first, even if the files are different, then it compares hashes. But since it uses an async function, a race condition can occur (though it is very rare).
I'll update/fix that code later.
Thanks for the report!
I'm very, very relieved! I was starting to fear that I was wasting your time with a false report and that it was due to me making an error and misremembering what I uploaded and that I did try to upload the wrong file the first time with one that actually did already exist.
Thank you very much for looking at that and finding that there was a cause for what I experienced!
Well you are the one to ever report this issue, so I guess destiny called :D
It would seem I frequently do common things in really uncommon and out-of-order ways. So much of my life has been spent troubleshooting and working out the causes for issues due to encountering these extreme fringe scenarios and circumstances that come as a result of my doing things in unexpected ways.
Maybe I unconsciously do things in strange ways and in an unusual order on purpose as I really do enjoy the challenge of solving the mystery and working out what could have led to the issue happening so that I can then think of how to fix it.
Thanks again, AOU!
Oh, just a quick question, did you get 'Upload title already uploaded' before or after the file was completely uploaded?
The upload progress dial was counting up as the elapsed time and time remaining counted up/down. The upload dial percentage got to about 92% and it then gave me that error popup when it looked like it was starting to load into the finished video page.
So I would say after it completed, but still did not say 100%. I think the last 8-10% of the upload might just be background configuration stuff and that the file actually does get fully uploaded at about ~92% on the progress dial.
(post is archived)