Jump to content

calbzam

Administrators
  • Content Count

    1,615
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by calbzam

  1. Hi, As you comment, I'm afraid the users will need to manually upgrade. The auto-upgrade feature will only work if the client and server version are not actually compatible. If they are compatible (7.0.16.X), I'm afraid that the auto-upgrade feature will not work. Regards, Carlos.
  2. Hi again, In order to restart your local macOS server: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Serverstartup sudo launchctl unload /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist sudo launchctl load /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist After that, the lock should be released. Regards, Carlos.
  3. Hi, We were not reported false positive issues specifically with Bitdefender in the past. We are going to report it to Bitdefender guys. We would appreciate if you do the same in the following link: https://www.bitdefender.com/support/what-to-do-when-bitdefender-detected-a-clean-file-as-infected-(false-positive)-851.html Regards, Carlos.
  4. Hi, If you restart your local Plastic server ("Plastic Server 6" under Windows services), is the issue still reproducible?The items may be locked for a few minutes due to this uncontrolled quit operation. Is the issue still reproducible today? In that case, we can try to manually release the lock in the cloud server. Regards, Carlos.
  5. Hi, are you paying customer? In that case, please reach us at support@codicesoftware.com so we can always assist you faster and even arrange a meeting session.Could you attach your "jet.conf"?Are your Jet databases stored at E:\? Could you create an "e:\jet" folder, move all the databases ("repositories", "rep_1", "rep_2"...) to the new location and edit the basepath in the "jet.conf" to the new location? You can check in the following link how to edit the jet database path: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#ConfigurePlasticSCMwithJet Finally, after editing the basepath, restart the Plastic server service and check if the issue persist.According to the error, it seems to be a problem with the path when the server tries to reach the databases. PD: If the issue is urgent, you can reach us at support@codicesoftware.comRegards,Carlos.
  6. You can remove/backup the file and when re-opening the GUI, a new clean "client.conf" will be created. Regards, Carlos.
  7. this issue is normally triggered by a lack of disk space when saving some changes. If you attach your file, we can try to fix it. Otherwise, you can remove/backup the file and re-configure the client again. It will automatically create a new "client.conf". Regards, Carlos.
  8. You can manually edit the ".plastic/plastic.selector" file to point to a branch and restart the GUI. eg: repository "MyProject@Myplasticlcoud@cloud" path "/" smartbranch "/main/Car Regards, Carlos.
  9. Hi, I think you may be affected by the following bug already fixed: [Bug] 8.0.16.3231 Windows - Visual Studio Package - Cloud Edition: The credentials dialog appeared every time you switch from using any Plastic GUI to Visual Studio plugin in Cloud Edition installations. Now it's fixed. Regards, Carlos.
  10. After deleting the "plastic.wktree", did you update your workspace? Note: As Pablo explained, your workspace selector needs to be pointing to a branch (not changeset). I don't understand why it doesn't work for you. You can always create a new local workspace and apply your changes in this new workspace. Regards, Carlos.
  11. Hi, 2. If the specific changeset id is not set, the workspace should be pointing to the head of the %BRACH%. Regards, Carlos.
  12. Hi, This is a local client configuration setting (not configurable on the server-side). By default, the "Pending changes" is not checking the file content (only the timestamp), because it would take a very long time in big workspaces with slow disks. Checking only the timestamp is very fast. Anyway, if you try to check in an item that appears as changed in "Pending changes" but the file content is actually the same (not changed), Plastic won't create a new file revision in the repository. Regards, Carlos.
  13. Hi, Is it possible that the file timestamp has changed? You can change this default behavior If you open the Plastic GUI --> Preferences --> Other options --> Check content to set a file as "Changed". Regards, Carlos.
  14. Hi, 1. If I properly understand you you to know the branch name based on the changeset id? cm find changeset where id=4619075 --format={branch} --nototal 2. You can also use a changeset instead of a branch name: eg: repository "%REPOSITORY%" path "/" smartbranch "%BRANCH%" changeset "%CHANGESET_ID%" Regards, Carlos.
  15. Could you attach your Plastic client logs from a machine where you face the issue? Is it happening in multiple machines? C:\Users\carlos\AppData\Local\plastic4\logs\plastic.debug.log.txt Regards, Carlos.
  16. We will report it to Microsoft. We have seen a similar issue in the past when some antivirus considered some of our binaries a virus by mistake. One question: Are you using Microsoft Defender (I guess in a Windows machine) and gtkplastic.exe (Plastic GUI for Linux)? Regards, Carlos.
  17. Hi, If the certificate is not valid/cannot be verified, could you generate a new certificate from another CA? (The Plastic SCM installation also includes a self-signed SSL certificate). Regards, Carlos.
  18. Hi, If I properly understand, you can switch to most of the branches/changesets with no issues (your encryption key is properly recognized) but when you switch to a specific changeset, you are requested to enter the key again and again? It sounds like this specific changeset was created with the wrong encryption key so you current key cannot decrypt the data and that's why you are requested to enter it again and again. Is it only happening to one specific changeset? Regards, Carlos.
  19. The custom path shouldn't be relevant. We have already created an internal task to better handle this scenario. Regards, Carlos.
  20. Ups, let me try to reproduce. We should better handle this scenario. Sorry for the inconveniences, Carlos.
  21. Hi @Danny, Please check the following feature: [New] 7.0.16.2589 filetypes.conf is now used for diffs and merges to check if a file is binary or text. Until now, the filetypes.conf configuration file was only used by the "add operation" to set newly added files as binary or text. From now on it will be used to determine if a file is binary or text before running diffs or merges. Example: suppose scene.config was wrongly added as binary. You can now configure filetypes.conf to consider scene.config as text, so the right text-based diff and merge tool will be selected instead of considering the "bin type" tracked for the file in the repo. Motivations: 1. This is really useful when you are working with Plastic Cloud, since changing revision types is not allowed there. 2. Our goal is to get rid of the bin/txt tracking as metadata in the repo, and rely only on filetypes.conf. You can configure a "filetypes.conf" and this way, you shouldn't need to start a new repo from scratch. Regards, Carlos.
  22. Hi, The "Pending changes" view already supports creating custom changelists: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide Regards, Carlos.
×
×
  • Create New...