I created a new repo with a Unity project, and can share it across client machines. Why does every single object along Main and its branches appear on both clients in red, unlike the rest of my repositories? What’s going on, and why doesn’t the client app give us any help or information?
Hi,
Could you attach a screenshot? Are you using the Plastic GUI or the Unity plugin?
Regards,
Carlos.
Apologies for the delay and lack of repro details
Steps:
- Create a Unity project (2021.3) in a folder next to other projects in source control
- Open PlasticSCM client (OSX)
- Select Open or create other workspace…
- Click Create new workspace…
- Click New…
- Create a repository [and select my server]
- Map the new repo to the project folder on disk
- Push the project to the repo
At some point, Plastic complained somewhere in the GUI that the repo was “not on disk” or some such nonsense, which clearly is not accurate, as the project started on my disk drive. Doh! I can’t seem to shake the strange red looking visualization, yet things appear to be working properly. Also, at one point, I was notified that I am not the owner of my project, which is alarming and so not accurate, AFAIK
Please lemme know what I should do…if anything. Sure don’t wanna lose my work!
Best regards,
///\ark.
Hi,
Each of these red items in the branch explorer are changesets. Every changeset is a snapshot of your project and for every checkin you perform, a new changeset will be created in your working branch.
If I properly understand, your guess was why the changeset color is red?
Regards,
Carlos.
That is my question, yes indeed. All other repo’s are green.
Perhaps this ambiguous error helps: I ran into it, fishing around the UVCS dashboard site, attempting to open the Billing settings tab. I am the (1) Administrator of my organization, so this error is…a defect. Please advise and report a bug if relevant here. Thanks.
In the Unity dashboard, the project that is in my new Plastic repo is not in the list for my organization. At this point, I suspect the UX flow that may work is to start by creating a project in the Unity Hub: I do not know, since I have not done this since Plastic merged with Unity.
At this point, I will continue to explore and guess the correct direction to flow from here. Advice is appreciated. Thanks in advance!
Hi,
Were these changesets replicated from a local repo? The default color for the changesets is blue but there are also branch explorer settings that could change the color.
The changeset color is not related to your subscription status. I don’t have your email to confirm it, but if your subscription was bought at plasticscm.com, you will need to manage the subscription, payment… from there.
Are you using also local repos? You can start the project in Unity Hub, Plastic GUI ir Unity plugin. But I’m afraid that It won’t make any change from the dashboard point of view or the projects listed there.
Regards,
Carlos.
Thanks for the information. I will ignore the billing related issues for now, having just noticed this new error message that asks me to create an organization…for some reason. I will go down that rabbit hole after resolving this thread Here’s a look at that other hole in the meantime…
Update:
I explored Project settings in Unity for the new project, and found that Services was not linked to a project ID. I created a project with the same name as the Unity project in the web dashboard, then linked it by selecting my Organization and the same name in the editor. That step appeared to work; However, after quitting Unity and restarting Plastic SCM client (OSX), the Branch Explorer looks the same, and even a bit angrier ;), and now, the error I was hoping would appear is there, yay! Apparently, my repo is “not on disk” again
What do y’all think?
Shucks. I am out and about with my laptop, wanting to do some coding, but hm. That might be risky. I’m going to zip up my repo, and attempt to download/clone the repo again. Since there is no home/house icon in the Branch Explorer, my assumption is that Plastic thinks it does not have the repo locally. Is that what the red color is supposed to represent, perhaps? We’ll find out shortly
Well, it turns out that even after cloning (downloading) the repo after deleting the local folder on disk via the Version Control client, the Branch Explorer looks the same, except that the home/house icon appears on the Main branch as it should. What now?? I’m just going to continue developing, and post any weird behaviours here. So far, so good? Any advice is much appreciated
I branched from Main/ and merged back into Main/ and things appear to be ok for now.
Why did you follow this workflow if the Plastic workspace was ok? According to your screenshot, some of the steps you followed remove the projects from disk.
From your previous comments, didn’t you already have a Plastic workspace up and running and you were able to submit changes?
I don’t fully understand what is the problem with it. Are you worried about the color of the changesets?
I’m guessing that the changesets were pushed from a local repo. Anyway, the color is not relevant from a workflow perspective.
Ok, thanks for the update.
Update: The OSX PlasticSCM client app still periodically shows that a repo is for no apparent reason. When this occurs, users are prevented from using features, such as those in the Branch Explorer. This is an issue. I would like to know why this occurs and what I can do to prevent it from happening. Please let me know if there is an active bug report that I can follow, if possible. Thanks!
Well, here it is again. I cannot work with my repo in this erroneous state. This looks clearly to be a defect at this point, perhaps specific to this operating system’s client. The repo shown below has been in the cloud for a while, and recently active, as you can see below. Where’s the little house that says I am at the tip of Main?
Also, I have never customized the Changeset colors (By user) so I can only guess that the red is actually randomly selected by the app/cloud platform and just appears angry to me cuz it’s red. If that’s the case, then I highly recommend never selecting red as a color in the default By replication source palette for a good UX design: It reads wrong/danger/error/stop by default for most folks.
So, I switched to every other repo in my Plastic SCM cloud account, and revisited the repo above. Magically, the repo is on disk and in sync with the right spot on Main. I have verified this is a defect. Perhaps it is unique to my account’s situation; However, I suggest Unity/Plastic dev’s reproduce and track. It’s certainly annoying and misleading. I will change my repo colors to the same one at this point, as far away from red as possible
Confirmed that to reproduce the broken/offline state of a repo, follow these steps:
-
Launch Plastic SCM app
-
Open a repo
-
Observe the repo appears to be and the Branch Explorer does not show the current workspace on any branch in the history
-
Press the reload (circle + arrow) button to refresh the Branch Explorer view
-
( Observe nothing changes )
-
Switch to another repo
-
Observe that the repo appears to be online and the Branch Explorer shows the workspace at the proper point
-
Switch back to the apparently broken repo
-
Observe that it is in working order
Please reply with a bug/defect tracking link, thanks!
Also, you can trigger the same function that initially fails by simply selecting the same repo from the top–left drop-down to the right of the house icon
P.S. Invitation for community incentive: Offer cloud credit for the time and effort users spend QA testing and reporting
Reproducible in version 11.0.16.7881 and prior
Not sure if I’m missing something but I don’t think this is a bug. When you open a repo, you are not creating a local workspace for this repo. You are just opening the branch explorer but you are not creating a local workspace or downloading the project on disk.
If then you switch to another workspace that is already on disk, you will be able to see the path on disk for this workplace.
In summary, opening a repo is not the same as downloading the repository (and creating a local workspace for it on disk). Opening a repository allows you to view the branch explorer but most of the operations will be disabled (switch to a branch, merge…). You will need to create the local workspace and download the project first.