Last modified: 2011-06-13 17:11:54 UTC
At least after an initial failed transcode, uploading a new version of the file does not seem to trigger a new transcode for the new version. No new entries to 'transcode' table are added, and there don't appear to be any new jobs for the job runner to pick up.
so fixed this in r89979 by removing transcodes and transcode state once a new version of the file is upload. Also have it doing the same thing for moving files. Future versions we may want to try and actually move derivative transcode files on rename.