-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to check out package - error when creating asset where a previous one was deleted. #111
Comments
Hey, thanks for the detailed report. Yes, I think that it's a well-known issue with Perforce & Plastic SCM (but also probably with SVN, and perhaps Git?) workflow; you cannot "add" a file that has been "rm" without a checking/submit/commit. I'll double-check how the Perforce plugin handles the case since it's the reference, but I have been using it for a long time and I think I remember hitting the same issue there. In any case, I agree that it would be a nice improvement to add this feature to the plugin, so I'll keep this in the backlog :) Cheers! |
A similar issue also appears when removing a directory that doesn't exist in source control. Repro steps iirc:
Inside plastic, the directory is listed for deletion, although it never existed in source control. I guess it's because the plugin told Plastic that there's a directory to delete and plastic doesn't verify if it even exists, or something like that. |
Thanks @sirjofri, would you mind opening a new issue for your issue? |
Ok, will do. I try to reproduce it before posting the issue, so it's more accurate 😉 |
Hey, thanks for the reply @SRombauts. It's been a while but I'm looking into this again because I'm trying to write some tools and I'm hitting this again...
Actually I just tested this - with the plugin disabled it appears to work totally fine. Not sure if I'm doing the same steps as you but here it goes:
This appears to work fine for me. Even trying different steps to change when things are checked out, it seems to work as long as the plugin is disabled. Would you be able to confirm this? Thanks! |
Add a Configure Rules button to the View Locks window #139
Hey there, thanks for your great work on this integration!
I'd like to report an issue when creating an asset with the same path as a previous one that was deleted.
Simple repro:
For me this will always result in this message and the asset creation will fail:
This seems to be an issue with asset creation in general as long as the created file is in the pending deletes in Plastic.
We're using 1.6.1 currently - if any more info would help please let me know.
Much thanks!
The text was updated successfully, but these errors were encountered: