Jump to content

calbzam

Administrators
  • Posts

    3,118
  • Joined

  • Last visited

  • Days Won

    115

Posts posted by calbzam

  1. 36 minutes ago, Francois Bertrand said:

    Mmm, maybe this is different in Gluon, in Plastic I just create a new workspace and "update workspace" to the latest version. If that's what you are saying, I did not realize in Gluon you had to specify files every time when starting a new workspace.

    Yes, please check the following guide: https://www.plasticscm.com/documentation/gluon/plastic-scm-version-control-gluon-guide#ConfiguringGluon

     

    36 minutes ago, Francois Bertrand said:

    In addition, it looks like in Gluon there is no way to tell which change set you are on? I guess you are always set to the latest on the branch you are on? Apologies for the noob Gluon questions! 

    In Gluon, the workspace selector is not pointing to any changeset. You could update a file to the latest version where some other files are out of date. You can update everything to the last or just the selected file.

     

    38 minutes ago, Francois Bertrand said:

    (do check out my question on "New changes available" not updating on certain actions, that one is legit I'm sure) :) 

    Could you clarify the details?

  2. Hi,

    It's a bit stange because it looks like the default configuration and we haven't been reported this issue in the past (other than this above message where recreting the VCS seemed to fix the problem).

    - If you remove the polling to manually run the build, does it make any change?

    - If you unckeck "Exclude default branch changes from other branches" does it make any difference?

    Otherwise, we will try to reproduce the issue in our labs. You are using SNAPSHOT-202210120016 of the plugin but what is your Bamboo version?

    Regards,

    Carlos.

  3. I can see a "wkcorruption" file in your shared folder related to the power outage.

    Process name: Unity
    Process image: C:\Program Files\Unity\Hub\Editor\2021.3.6f1\Editor\Unity.exe
    Process started: 2022.11.02.12.31.33.673
    Error: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index
    StackTrace:   at System.Collections.Generic.List`1[T].get_Item (System.Int32 index) [0x00009] in <e40e5a8f982c4b618a930d29f9bd091c>:0 
      at System.Collections.Generic.List`1[T].System.Collections.IList.get_Item (System.Int32 index) [0x00000] in <e40e5a8f982c4b618a930d29f9bd091c>:0 
      at Codice.CM.WorkspaceServer.DataStore.WkTree.ReadLegacyWorkspaceTree.ReadNode (Codice.CM.Common.Serialization.PlasticBinaryReader reader, System.Collections.IList repSpecs, System.Collections.IList seids, Codice.CM.WorkspaceServer.IWorkspaceRevisionInfoCache cache, Codice.CM.WorkspaceServer.DataStore.WkTree.LegacyWorkspaceTreeOptions+Options options) [0x00018] in <98f66477eed44bb782eb0c301b0da195>:0 
      at Codice.CM.WorkspaceServer.DataStore.WkTree.ReadLegacyWorkspaceTree.ReadFromStream (System.Byte version, System.IO.Stream stream, Codice.CM.WorkspaceServer.IWorkspaceRevisionInfoCache revisionCache) [0x00026] in <98f66477eed44bb782eb0c301b0da195>:0 
      at Codice.CM.WorkspaceServer.DataStore.WkTree.ReadLegacyWorkspaceTree.Read (System.Byte version, System.Int32 treeSize, System.IO.FileStream fileStream, System.Byte[] dataBuffer, System.Int32 dataOffset, System.Int32 dataSize, Codice.CM.WorkspaceServer.IWorkspaceRevisionInfoCache revisionCache) [0x00043] in <98f66477eed44bb782eb0c301b0da195>:0 
      at Codice.CM.WorkspaceServer.WorkspaceTreeDataStore.ReadWorkspaceContentFromFile (System.String filePath, System.String wkPath, Codice.CM.WorkspaceServer.IWorkspaceRevisionInfoCache revisionCache, Codice.Utils.Buffers.FlexibleBufferPool bufferPool) [0x000f0] in <98f66477eed44bb782eb0c301b0da195>:0 
      at Codice.CM.WorkspaceServer.WorkspaceTreeDataStore.ReadWorkspaceTreeContent (Codice.CM.Common.WorkspaceInfo wkInfo, System.String wkTreeFile, Codice.CM.WorkspaceServer.IWorkspaceRevisionInfoCache revisionCache, Codice.Utils.Buffers.FlexibleBufferPool bufferPool) [0x00008] in <98f66477eed44bb782eb0c301b0da195>:0 

    I would update the workspace first to to point again to the head of the branch. But please backup your pending changes first.

    Regards,

    Carlos.
     

     

    • Like 1
  4. Hi,

    I'm guessing if these outage also affected to the workspace metadata so it's not properly tracking now what changeset/branch is your workspace pointing.

    The workspace metadata folder is the ".plastic" folder in the root of the workspace. Can you attach it?

    For that reason, it's asking you to update your worksapce (probably it's considering you are in changeset:0).

    If you have some pending to checkin changes, I would backup them and then update the workspace to the head of the branch (or even redownload the project from scratch if it's not a big project).

    Best reagrds,

    Carlos.

    • Like 1
  5. Hi,

    Was the file timestamp changed? By default, Plastic is detecting as changed a file when the file time stamp changes. You can edit this at Preferences --> Other options:

    image.png

     

    Also in the diff comparation method, please check that you are not ignoring any actual change in the file: EOLs, whitespaces.

    image.png

     

    Regards,

    Carlos.

×
×
  • Create New...