Freesound Forums

Every time I upload a longform recording and describe it, I get django/nginx errors. The upload goes fine, but submitting the description page destroys the file. It stops showing up in any of my "Manage sounds" pages. Presumably, the copies of it are still on your server eating space...

EDIT: Hours later, the problem seems to have resolved itself.

Hi,

The sound was not anywhere in the manage sounds page, but then it appeared after a while or you re-uploaded completely? Did it happen more than once?

https://freesound.org/people/strangehorizon/sounds/710978/

I uploaded & described this one 3 complete times before it actually showed up. The first 2 times, the file simply vanished.

Do you have any idea about the approximate time when you tried the first 2 times? I'll try to correlate this with some of our error logs, so far I'm not finding anything obvious.

Nope, I only remember that the 2nd instance occurred shortly before posting the thread. So, about 15h ago at the time of this writing.

I'm uploading another long rain recording now to see how it does.

Thanks, I just found two matching error messages, I'll investigate and fix the bug.

Right on. This last one just entered the processing queue without issue.

I found the bug, I'm deploying a fix right now. The problem would happen when describing sounds right after they are uploaded, fast enough so that their pre-description processing stage (something that we do in the new UI so that we can show the sound player in the description form) was not finished. This would basically affect long sounds for which the processing time could be longer. I suspect you did not see the sound player in the description form right? You'd see something like "player can't be shown right now". Anyway, this should not be a problem anymore and no more sounds should be eaten (at least this way!). Thanks a lot for reporting, this one would have been hard to detect otherwise

Yes, I have also sometimes seen the waveform suddenly appear while describing a sound.

I can't edit thread titles to mark this one as fixed. Maybe you'll want to do it.