-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issues with Git Pull #467
Comments
@michael-rust thanks for filing this, helpful to have as a reminder. |
Can you see if the git pull records anything in the application error log? This may be related in part to #457 (re: the uncompiled state). |
Yes, there was this error: " 127 Pull+1^SourceControl.Git.API.1". The full application log is attached. |
Ahh - this is highly relevant. Can you try reinstalling git-source-control via standard zpm "install git-source-control"? I think you have a snapshot of 2.4.1 prior to actual release. |
Is there a way to confirm the install? When I go to the git settings it says package version: 2.4.1 |
@michael-rust good question - ultimately it's a matter of our practices in this git repo; we haven't generally put a -SNAPSHOT designation on the main branch between releases so there isn't any delineation between something-that-could-be 2.4.1 (installed via If you |
Okay sounds good. I'll report back the next time we do a pull. Thanks for the quick responses. |
I'll keep an eye out - thank you for nudging on this publicly! |
Hi Tim, After installing the latest package we're still seeing the following issues with the git pull:
The issues listed above only happen sometimes, other times it all works perfectly, which I know is a troubleshooting nightmare. |
Root cause: |
This mapping issues most likely explain the problems with indication of pull success as well, but it would be worth double checking the error handling to make sure we're not just relegating useful output in the application error log in event of a serious failure. There appears to be a secondary issue with preview output being displayed (from testing in my own HCC environment) - need to investigate this, and specifically to make sure that there's always some output. The issue in that environment could also be similar depending on the mapping techniques being used there. (This still needs triage.) There is another cause for files not being loaded (!) or compiled independent of #457: with a large set of files changed, some in subfolders common among changes, if output has .../ it isn't processed properly. We need to update this to properly interpret as a relative folder. |
With improved logging (from work in progress) the .../ issue could end up looking like:
|
We consistently see an issue where we start a git pull from the IRIS for Health homepage and there is no indication if the pull finished successfully or with errors.
When we look at the classes that were pulled in they are in an uncompiled state.
See screenshots attached.
IRIS version: IRIS for UNIX (Red Hat Enterprise Linux 9 for ARM64) 2024.1 (Build 263U) Wed Mar 13 2024 15:32:09 EDT [Health:7.2.0]
Git package version: 2.4.1
GitPullIssues.docx
@isc-tleavitt notes on aspects of this:
The text was updated successfully, but these errors were encountered: