Title says it all. The Unity editor plugin checkout / undo also do not work, so it’s not a bug with the standalone client GUI. Just updated to latest version. The issue persisted. Also notice that it’s not every file. Just that scene file.
I also had this issue happen with another larger prefab file <=10min before this bug. To fix it, I ended up deleting the file and trying to press undo on the deletion. I got the error “No connection could be made because the target machine actively refused it.” I restarted my computer, then undoing the deletion worked. Lost my changes, but I didn’t want to commit them anyways.
My guess is that it’s something server related? Except, I need those changes checked-in to my repo.
Really need a fix to this because I can’t check-in my work. Thank you for your help.
Couldn’t get the file to get checked out, undone, or pushed up, so I ended up deleting the file and undoing the deletion to restore the file.
I then re-applied my changes to the scene in the editor, and in the Pending Changes tab it marked the scene as “changed” but not checked out. Nothing unusual yet. But, once again, I was unable to directly check out the file or undo it. And as a result, I was unable to commit the changes to the repo.
So then, I did the song and dance of deleting and undoing the deletion to clear the changes.
It was at this point that I noticed a peculiar detail. In the Workspace Explorer, while having no changes to the Title.unity scene… it reports the scene as being checked-out?
My current suspicion is that there is some corruption within the .plastic folder of this workspace. The workspace did hit a System.OutOfMemory exception the other day because I was running too many programs (not plastic’s fault). I had to go in and restore the plastic.wktree.bak file.
So… perhaps I need to just clean up the .plastic folder? …is there any way to do that?
Because I can’t waste any more time, I decided to just bite the bullet and reset my repo entirely. I shelved my changes, deleted .plastic, created a new workspace in the same directory, updated to the latest changeset, then downloaded my shelved changes again.
For those that have encountered a similar issue to what I described above… you’ll probably need to reset your workspace unless there’s some way to perform surgery on your .plastic folder (or another folder I don’t know of).
Sorry for the delay in response. Glad to hear you were able to workaround it.
If this scenario represents itself again, then please log a support ticket with us. It would be great to identify the cause of the issue. Also, I suspect you will be able to “perform surgery on your .plastic folder” to retain the workspace, as you say.
