Jump to content

calbzam

Administrators
  • Posts

    3,118
  • Joined

  • Last visited

  • Days Won

    115

Posts posted by calbzam

  1. Hi,

    Sorry for the delay. After reading your explanation, I still don't fully understand the use case.

    Could you include some example so we can fully understand your workflow?

    In Plastic, you can use Xlinks, if you want to link an external library/repo into your project. The Xlink will be pointing to a specific version of the library/repo https://docs.plasticscm.com/xlinks/plastic-scm-version-control-xlinks-guide

    It's possible even to share the same library/repo between different projects: https://blog.plasticscm.com/2014/08/how-to-share-engine-repository-between.html

    Regards,

    Carlos.

  2. Hi,

    It seems that somehow you replicate the history of the "UIStateService" into the "UIToolkit" repo. 

    Could you check with any of the users with access to the repo if they run any replica operations? Are you replicating repos in your workflow?

    Could you review the changeset guids of any of these replicated changesets to check if they are the same changesets guids in the original "UIStateService" repo? This will clarify if what happened is actually a replica between the repos.

    Regards,

    Carlos.

  3. 10 minutes ago, Lexderi said:

    I get singed out every day and it says "You have probably been sign out due to inactivity" (cant provide screenshot because I already have signed in today)
    404 errors also pop up until I sign in again

    I also use unity ID to sign in

    Please make a screenshot the next time it happens and also share the logs with us leting us know the estimated time it happened:

    C:\Users\xxx\AppData\Local\plastic4\logs

    10 minutes ago, Lexderi said:

    The mapping also doesn"t seem to work

    image.png.a6289263e4f2431c439ac6b4a0bdb8bc.png

    The git user was adrian@rummert.de (same email as this plastic acccount)
    On plastic it also doesn't show any owner (even for changesets that have an owner (my friend) in github)

    Not sure if you can temporary allow us some access to a git repo to try to reproduce the issue with the owner not being considered.

    Regards,

    Carlos.

  4. Hello,

    - You perform this change on git and then you sync it to Plastic?

    GitSync allows you to map git users with Plastic users: https://docs.plasticscm.com/gitsync/plastic-scm-version-control-gitsync-guide#Mappinguseraccounts

    What was the git user who performed the commit? On a normal basis, Plastic should be able to use the git owner to store the changeset owner in Plastic. Doesn't this git commit have any owner?

    - Anyway, Plastic shouldn't log out any user that is properly configured in the client. We don't have such a feature to log out inactive users in the Plastic GUI. Could you include some details, logs, screesnhot...? The Plastic GUI client authentication is independent to the GitSync operations so may be running.

    Regards,

    Carlos.

  5. Hi,

    The Version Control package is not supported in Linux. I would be very careful using it and use the standalone Plastic SCM client instead.

    Regarding your issue: are you using the "ignore.conf" in your Unity project? If Plastic is tracking some files as deleted + add most probably they were removed and recreated so the timestamp is different. Plastic is tracking your changes on disk and trying to match what happened.

    Regards,

    Carlos.

  6. How are you reproducing this issue? Could you let us know the steps so we can try the same?

    Quote

    So you are using the macOS Plastic GUi for the first time against a cloud encrypted repo and you are not being requested to enter the encryption password, right?

    Are using Plastic for the first time against a new encrypted server? This was the initial issue in this post.

    Regards,

    Carlos.

  7. Hi,

    This recent fix shouid be useful, right? https://www.plasticscm.com/download/releasenotes/11.0.16.7665

    Quote

     

    All clients: Incoming Changes respects the cloaked rules.

    Before, the Incoming Changes operation downloaded the files/directories although they were under cloaked paths. This was inconsistent with the update operation behavior and with the cloaked semantics themselves.

    Now, the changes under cloaked paths are skipped like the update operation does.

    The Gluon Incoming changes is not affected by this behavior (cloaked rules don't make sense in Gluon) since the operation works in a different way.

     

     

    On 12/20/2022 at 2:18 PM, Jashan Chittesh said:

    Another issue that I just saw: When removing the folder from the cloaked.conf file, instead of downloading the files next time I refresh in Plastic, the folder is shown as deleted. I can see why this happens and I can get what I want by using Undo ... but it's not a great UX because there is quite a risk that someone accidentally checks in deleting the art folder.

    Can you confirm if this behavior still happens after upgrading to the latest Plastic version? We will evaluate it.

    Regards,

    Carlos.

  8. Hi,

    What is the changeset id of the second head you need to merge?

    mount:56e62dd7-241f-41e9-8c6b-dd4ca4513e62#/airogames_lifeofdelta@local merged from: Merge 1134
    mount:56e62dd7-241f-41e9-8c6b-dd4ca4513e62#/airogames_lifeofdelta@local merged from: Merge 1122

    This format looks good, but there should be just one entry for the changeset id you want to merge.

    Regards,

    Carlos.

     

  9. Hi,

    Let's try the following. If you tried to merge these changesets and actually there is nothing to be merged:

    I have a workaround to unify the heads. Hack the client to send a merge link meta information in order to set the changeset as "merged" and allow you the replication.
    You will need:

    1) Switch your workspace to the destination branch.
    2) Create a file called "plastic.merges" at your "wkspaces<Your_workspace>.plastic" hidden path.
    3) Get the changeset multiple head list.
    4) Add the following content.

    mount:56e62dd7-241f-41e9-8c6b-dd4ca4513e62#/#<Repo_Name>@<Server_IP_Or_Name>:8087 merged from: Merge <CSET_ID>
    mount:56e62dd7-241f-41e9-8c6b-dd4ca4513e62#/#<Repo_Name>@<Server_IP_Or_Name>:8087 merged from: Merge <CSET_ID>
    ......
    


    And replace the "<XXX>" fields by its actual value for you:

    <Repo_Name>: Repository name.
    <Server_IP_Or_Name>: The server IP Address o the server name
    <CSET_ID>: The changeset numbers you have determined as the multiple heads candidates.

    After creating the file and saving it you'll see the pending changes view with a few new pending merge links, you'll be able to check it in and workaround the issue.
    Tell me how it goes!

    Regards,

    Carlos.

  10. Hi Olaf,

    The release notes refers to the fact that cloaked rules cannot be applied in a Gluon workspace because the workspace structure is very different than a regular Plastic workspace. cloaked.conf rules are not working on a partial workspace.

    It doesn't mean at some point it could be added a feature to easily configure the Gluon workspaces per file type...

    Regards,

    Carlos.

  11. Hi,

    The incoming changes notification is recalculated every minute. It's also recalculated when you change the window focos or when you perform some operations in Gluon that involces recalculating the incoming changes.

    The refresh buttons are refreshing the view you have opened: Explore workspace, Checkin changes... but it's not related to the incoming changes calculation.

    On 11/14/2022 at 2:59 PM, Francois Bertrand said:

    after "Update workspace", we STILL see "new changes available", even though there are no more changes available..., giving the impression that "update workspace" DIDN'T update

    I haven't seen this behavior in the past but I will try to reproduce. Can you consistently reproduce it?

    Regards,

    Carlos.

  12. Hi,

    The incoming changes notification is recalculated every minute. It's also recalculated when you change the window focos or when you perform some operations in Gluon that involces recalculating the incoming changes.

    The refresh buttons are refreshing the view you have opened: Explore workspace, Checkin changes... but it's not related to the incoming changes calculation.

    Regards,

    Carlos.

×
×
  • Create New...