Written by

Question Gautam Rishi · Jun 19, 2023

getting an error while installing git-source-control

getting an error while installing  git-source-control
Log of error 
 

zpm "install git-source-control"

[TTN|git-source-control]    Reload START (/Users/irisusr/mgr/.modules/TTN/git-source-control/2.2.0/)
[TTN|git-source-control]    Reload SUCCESS
[git-source-control]    Module object refreshed.
[TTN|git-source-control]    Validate START
[TTN|git-source-control]    Validate SUCCESS
[TTN|git-source-control]    Compile START
[git-source-control]    Compile FAILURE
ERROR! Error registering reference '^Studio.SourceControl.ChangeI("$Change")' for use by 'SourceControl.Git.Change.cls': <PROTECT>IncompatibleUse+3^%ExtentMgr.GlobalRegistry.1
  > ERROR #5030: An error occurred while compiling class 'SourceControl.Git.Change'

Comments

DC AI Bot · May 25 Bot

This error has been reported in a similar installation scenario, and one documented resolution was that the issue was tied to $System.OBJ.Load() on IRIS 2021.2; after upgrading to IRIS 2022.1, the problem went away. [1]

A suggested recovery step from the same report is to clear the namespace source control class first by running:

do ##class(%Studio.SourceControl.Interface).SourceControlClassSet("")

then reinstall git-source-control, and after that re-enable SourceControl.Git.Extension as the source control class for the namespace. [1]

For diagnostics, the same source suggests:

  • Force single-process compilation:

    Do $System.OBJ.SetQualifiers("/nomulticompile")
  • Force single-process package load:

    zpm "install git-source-control -DThreads=0"
  • Capture detailed object load errors with:

    zbreak *%objlasterror:"N":"$d(%objlasterror)#2":"s ^mtempdbg($i(^mtempdbg))=%objlasterror"

    and then inspect ^mtempdbg to see where the bad %Status is coming from. [1]

So, based on the retrieved material, the practical next steps are:

  1. Clear the source control class with SourceControlClassSet(""). [1]
  2. Retry the install, preferably with -DThreads=0. [1]
  3. If you are on IRIS 2021.2, consider upgrading to IRIS 2022.1 or later, since that resolved the reported issue in the cited case. [1]


Sources:

Tell us more:
Don't like the style
Not factually correct
Didn't fully follow instructions
Refused when it shouldn't have
Being lazy
More...
Submit
0 0