-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional info in the welcome screen #613
Comments
All of that sounds like very useful info! However, I think it makes more sense to have it be available when the terminal shell is started (can be done via the ZSTART routine I believe) and doesn't belong on the IPM side |
Related to the welcome screen. It reports only
Even I have two other active registries:
|
The challenge is I end up supporting the module definitions and the folks that report issues either arent interested or dont know how to do such things. Certainly not a threat but I feel like I have to add custom |
Ultimately I don't think the zpm welcome screen is the place for this. Really it all belongs in the InterSystems Diagnostic Report (https://docs.intersystems.com/iris20242/csp/docbook/Doc.View.cls?KEY=GCM_diagnostic) or your own equivalent; you should be able to just hit a button to get this rather than going into terminal. At some point I'd imagine the InterSystems diagnostic report having IPM-related information in it as well. |
@SCanzano , alternatively you can build your own terminal client dependent on zpm-client. |
while it likely is good to have the diagnostic report show this information my original inquiry is because
or
|
When you start ZPM you get something like
========================================
|| Welcome to the Package Manager Shell (ZPM). version 0.7.3 ||
|| Enter q/quit to exit the shell. Enter ?/help to view available commands ||
|| Current registry https://registry.readycomputing.com/registry ||
Often times I get issues reported to me about FAILURES that occur with an install.
I'm making a recommendation that the above screen show additional information like
the results of $ZV or if in a HealthShare installation the full HealthShare version string
whether or not this is the primary mirror member if part of a mirror or if on a backup
the results of what is found in
Set $Namespace = "%SYS" $$$THROWONERROR(tSC, ##class(Config.Startup).Get(.tProperties)) Set pSystemMode = $Get(tProperties("SystemMode"))
so that we could see if this is a TEST, STAGE or PROD environment.Maybe some information about the %SYS("HealthShare","Instances" types so we can see if this might be an instance where HSANALYTICS, HSPI, the CV etc are currently installed. This is important because InterSystems does not deliver all of the code to each HealthShare instance but rather only the code that is appropriate for the instance type. Some of our modules have dependencies on things like HSPI_Data.Patient and can only compile if the instance has HSPI installed.
Having this information might prevent me from having to ask for additional informaiton if we make it easier for people to capture.
The text was updated successfully, but these errors were encountered: