We're pretty sure we have this fixed for the upcoming release - it appears to be a race condition that we've addressed by changing some asyncronous operations to be syncronous.
Vivek has been able to clean this up by forcing the deployment to update from the staging tab. You can do that by changing the post the deployment is using, then changing back to the original post, and clicking "Update".