search

NRC-Research / SNAP-issues

This repository was created to provide a public location to record and display the status of "issues" for the SNAP application. The SNAP developers will acknowledge, provide (and maybe request) feedback on the reported issues, and in general use the information to improve SNAP code.
3 stars 0 forks source link

RHEL based SNAP-git plugin issue #24

Closed NRCgg closed 2 years ago

NRCgg commented 2 years ago

When trying to clone a repo from github using the same SNAP version as works under windows, there is an error thrown:

[Tue Feb 22 17:40:41 EST 2022] Error: Clone failed. https://github.com/NRC-Research/SNAP-Sample-Models.git: cannot open git-upload-pack

This is using v 2.2.1 of the git-plugin with the same version of git.jar plugin that works under windows. Surprising!

NRCgg commented 2 years ago

After careful cleanup and careful re-installation and copying the appropriate jar files into the plugins directory, turning debugging on in the LauchConfig - I discovered that the model editor was still trying to use a proxy! I did a sweep of all of my files and found that I had an old eclipse directory that had the proxy information setup. I deleted all of the eclipse files (and many other files that had the proxy information) and then got a new error:

Set the GCM_CREDENTIAL_STORE environment variable or the credential.credentialStore Git configuration setting to one of the following options:

secretservice : freedesktop.org Secret Service (requires graphical interface) gpg : GNU pass compatible credential storage (requires GPG and pass) plaintext : store credentials in plain-text files (UNSECURE)

So, I edited my /etc/gitconfig file to set the GCM store option:

$ cat /etc/gitconfig [filter "lfs"] clean = git-lfs clean -- %f smudge = git-lfs smudge -- %f process = git-lfs filter-process required = true [credential] helper = manager-core credentialStore = gpg

and made sure I had gpg and pass installed!

After this the GCM popped up a window asking for gpg password! I entered the password and it worked!

Closing this "bug" - was really a miss-configuration!