Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


karmakat last won the day on January 16

karmakat had the most liked content!

Community Reputation

1 Neutral

About karmakat

  • Rank
  1. Hiya, I am looking for a way to query a revision in a changeset for a file that had the operation "Moved" at checkin time. Basically, I want to know the path it was moved from and the path it was moved to. This is different from the "cm status --moved" which will only report what is going on in the current workspace before a checkin. Is this possible? Thank you in advance!
  2. Hiya, Is there any way to see the operation applied to a revision in a changeset? Ie, can I format my cm -ls command response to show whether a file has been Added, Deleted, or Moved? Thanks in advance!
  3. Hi @calbzam, I have tried as you suggested, putting the log file on the desktop, and I also tried the appender type you have here which is different from what @manu suggested. And, the "plasticapi.log.conf" has been in the client folder throughout my testing. Unfortunately I am still not getting any logs when I run "plasticapi" from an elevated command prompt.
  4. Hi @manu, I am trying to run the plasticapi from the same computer the server is running. There really shouldn't be any issues with permissions especially considering the server and the control panel is working within our domain already and can be accessed from other systems in the domain. The netsh commands I have tried: netsh http add urlacl url=http://X.X.X.X:9090/ user=Everyone netsh http add urlacl url=http://+:9090/ user=Everyone netsh http add urlacl url=http://X.X.X.X:9090/ user=specificUserExample Another thing is that you seem to be only able to run this once for a URL or you will get an error like so: Url reservation add failed, Error: 183 Cannot create a file when that file already exists. I have tried as you suggested to create the "plasticapi.log.conf" file where the "plasticapi.exe" file is located. However the destination log file does not seem to get any data. I have tried several configs for the the file itself. Permissions seem fine on the log file. My command for the running the api process is simply to run the plasticapi.exe from the command window. I have also tried with just about every combination of flags and ports but always get the same result: Unable to start the REST API listener. Please make sure that you have HTTP permissions for the current port and user. I am totally stumped here as to why this is not working. The user is an administrator. The cmd.exe is run as administrator. Windows Firewall is off. I have tried disabling antivirus. Without any log information, we have no ability to troubleshoot this issue..... only this Unable to start the REST API listener message. Any help at all would be much appreciated since this is a complete blocker for our pipeline development.
  5. Hiya, I'm pretty sure this is more of a general networking issue, but I am hoping to get any tips on how to troubleshoot this issue. The problem is that I am unable to start the plasticapi.exe rest api on our server, running Windows Server 2012 R2. It is a most basic installation. I get the following message: "Unable to start the REST API listener. Please make sure that you have HTTP permissions for the current port and user." I am running this in a command prompt with elevated privileges The server is already accessible in our network using the client The server control panel is accessible in the browser using port 7178 The hosts file has line un-commented Ran the command: netsh http add urlacl url=http://+:9090/ user=myusername Windows Firewall is disabled. Not sure what other steps could be taken to troubleshoot. Event logs in windows show nothing out of the ordinary. What could we be missing? Thanks in advance!
  6. As the topic says: Branch explorer renders an incorrect placement of a "home icon" signifying local changes in an uncommitted changeset. Developers here at our studio have flagged an issue in the windows PlasticSCM client application wherein the grayed out home changeset icon can appear incorrectly in the past in the UI. Sometimes it goes so far to the left it is no longer clear which branch you are currently on without leaving the Branch Explorer view to visit the Branches list. This issue has been a thorn in the side for around 6 months, before which time it was not an issue in the client. It has caused a good deal of confusion here in house, especially when on-boarding contractors who are new to PlasticSCM. I have attached some images for reference: This last screenshot shows how far back this problem can occur, being an entire "page" to the left.
  7. Hiya, Following up on our chat and add some clarity to my post above and the workarounds... There is a workflow issue wherein if you have a file nested within a cloaked directory, and the parent folders do not already exist in a local workspace, you cannot run an update using the command line tool and the "--cloaked" flag for a specific item path . It will result in a message like: "Could not find a part of the path to ...." . Since Plastic is currently looking for the parent folders to exist upstream of the file location in the workspace, you would have to drill down folder by folder from the root, pulling down the entire contents of each of those folders. The workaround is to use only a local workspace "cloaked.conf" and not a global one, and edit this cloaked.conf to remove all the folders that may be cloaked temporarily before running the update command. After running the update, you may add these folders back into the "cloaked.conf". Ideally, PlasticSCM would implement a feature that out-of-box, you are able to update / getfile for any valid repo path, whether it is cloaked or not. It still makes sense that the "--cloaked" flag would be required for any file that is cloaked or is nested within cloaked directories.
  8. Sure! Let me know if I can prepare anything to help.
  9. Hey Manu, Sure! I am in Toronto, EST. Let me know over PM I guess some times that work for you and let's chat! Thanks! - Aleks
  10. Hi all, I want to follow up after I've spent sometime working with the cloaked.conf feature. I've had some successes and some issues and workflow challenges. Cloaking an xlink directory does not work. Even updating the workspace at root ( "." ) using the --cloaked flag fails to pull the contents of the xlink. The xlink will never appear again in the workspace, even if it is removed from the "cloaked.conf". Therefore, it can also not be deleted. This seems like a bug more than anything. The "solution" to the above point is to add all the folders under the xlink to the cloaked list. Now when updating using the "--cloaked" flag from the root, the entire workspace is updated. Cherry-picking updates in a cloaked directory structure does not work. Requesting anything that is not already on disk in the workspace results in the error that that path is not in a workspace. Ie. If you have a file in the path of "xlink/Assets/Props/thing.fbx" and try to update this file when "Assets" folder is cloaked, the operation will fail. I strongly feel this last point is serious weakness of PlasticSCM, certainly in the workflow I need. I need to maintain a contiguous folder structure between work in progress Art assets, and development, so these wip assets can interact with assets in the game engine in a sort of sandbox paradigm, without actually being part of the same repo. We obviously do not want to have to pull down the entire art repo when doing development, hence using the cloak feature. This means I will need to pull down everything in the "xlink/Assets/Props" folders just to get my single file updated. The solution I think is that I will have to remove the "xlink/Assets" folder from the local workspace's "cloaked.conf", run my cherry-pick update, then add the "xlink/Assets" folder back to the "cloaked.conf". At least this should work to accomplish my workflow. I have some more dev to do to accomplish this, but in theory it is the work-around.
  11. Thanks Manu! This is exactly what I'm looking for. I will test it out to make sure it's appropriate for our workflow. I've noticed also that the cm.exe update command has a flag for --cloaked, so you may force an update of cloaked items, so I believe that will allow me to do what I need to.
  12. checkout: Unexpected option --exclusive

    Thank you Manu!
  13. I am having some trouble finding clear documentation on the following: - Is it possible to update a workspace, but NOT a writable xlink? - Is it possible to update an xlink directory, but nothing else in a workspace? Thanks in advance!