asdasdasd

Isn't being able to connect to the plastic SCM pretty basic functionality? What use is plastic if it cannot connect to the plastic SCM server?

This is not entirely ideal. A kind suggestion from my side: Ensure error messages are not done away with, for whatever reason, milliseconds before appearing. They are kind of important for users to understand why an action was declined or did not resolve as expected.

I find some of the information in the GUI to be inaccessible and confusing and a lot of my issue-resolving has consisted in tinkering with options and features for hours until the cumulative effort appeared to resolve the issue, but leaving me in the dark as to what exactly the issue was caused by and what measures specifically lead to its resolution.

Super cool, thanks plastic for having me spend countless hours trying to fix your bs while I could be working on my project! Really the bees knees of version control software!

Let me also add how amazing it is that when you start downloading a repo of 500Gigs, plastic closes every window and application (seemingly?) and just dissappears so you don't even really know what's going on with it. You can still tell by the smell that slowly starts filling the air of your workspace, but other than that you have no way of checking in on plastics progress, because it dissappeared entirely and were it not for the smell and task manager, you wouldn't even know it's still working. This is testament to the quality of plastic, being able to see information on operations being performed just gets in the way of the ever so enjoyable everyday struggle of solving exceptional errors in plastic. Super exciting stuff.

I reinstalled and the issues persist, oh the joy! Such a wonderful helpful tool empowering developers.

Dealing with plastic has probably cost me about 30 hours of unpaid time struggling, reinstalling, trying to fing solutions, trying to hack and outsmart the software in hopes of getting it to do what should come naturally to it (what it's meant to do, presumably) over the past week or so. I'm baffled by how terrible it is. After fixing problem A (Having to manually restart the plastic service after comitting some files caused Plastic to throw an error because comitting files is a highly infrequent and fringe operation thus it can be expected that there's sometimes issues with it, I guess?) and I have now successfully moved on to needing to fix problem B in order to use this garb useful tool. Can't wait to see what Problem C and D further down the line will look like, I'm sure it will be super exciting to try to deal with those. Problem B consist in the following: - I start Plastic - There's changes available as indicated in the top right (I lick view) - Before the changes can even be loaded, I am shown this highly encouraging error message: Now that's very funny because firstly I believe I had checked that asset back in succsessfully before Plastic started giving me trouble, and secondly I was the one that checked it out and it is my email that is shown in the error message. So me having checked out an asset throws an error when trying to view pending changes to a workspace? Is that not a normal operation for version control software? Do you guys need some help perhaps on the software side of things to implement a feature that doesn't cause basic operations to throw errors? I don't even know where to start. I guess I'm uninstalling and reinstalling it for the fourth time this week. Awesome! You guys have truly made wrestling with SVN software instead of doing actual work a fulltime activity, you should be proud of yourselves.