Hi Jakob, Thanks, that did the trick. I had done
pip install keyring so when I did yum install python2-keyring I ended up with a frankenstallation, since both mechanisms write to the same folder, and things were even more broken than before. However, doing yum remove python2-keyring pip uninstall keyring yum install python2-keyring straightened things out again and I was able to move on to the next problem 😅 Cheers, Loris Jakob Schiøtz <[email protected]> writes: > Hi, > > I remember having this problem at one point. You have to have the key ring > package installed outside of EasyBuild, in the system Python that EasyBuild is > using itself to run. And that was a bit tricky because the version you get > with > pip does not actually work with a Python 2.7. I think the solution was > installing some package systemwise, probably python2-keyring, but I honestly > cannot remember it. > > Best regards > > Jakob > > > -- > Jakob Schiøtz, professor, Ph.D. > Department of Physics > Technical University of Denmark > DK-2800 Kongens Lyngby, Denmark > http://www.fysik.dtu.dk/~schiotz/ > > > >> On 13 Mar 2020, at 11.52, Loris Bennett <[email protected]> wrote: >> >> Dear Kenneth, >> >> Getting the token back out of the keyring seems to fail: >> >>>>> import getpass, keyring >>>>> keyring.get_password("github_token", "tardigradus") >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> File "/usr/lib/python2.7/site-packages/keyring/core.py", line 57, in >> get_password >> return _keyring_backend.get_password(service_name, username) >> File "/usr/lib/python2.7/site-packages/keyring/backends/fail.py", line >> 24, in get_password >> raise RuntimeError(msg) >> RuntimeError: No recommended backend was available. Install a recommended >> 3rd party backend package; or, install the keyrings.alt package if you want >> to use the non-recommended backends. See https://pypi.org/project/keyring >> for details. >> >> What can I do to move forward with this? What recommended 3rd party >> backend can I use? I didn't install 'keyrings.alt' because the warning >> didn't really enlighten me. Should I try that? >> >> Cheers, >> >> Loris >> >> Loris Bennett <[email protected]> writes: >> >>> Dear Kenneth, >>> >>> Here's the relevant part of the log: >>> >>> == 2020-03-06 07:37:29,260 build_log.py:265 INFO * GitHub user... >>> * GitHub user...== 2020-03-06 07:37:29,260 build_log.py:265 INFO >>> tardigradus => OK >>> tardigradus => OK >>> == 2020-03-06 07:37:29,260 build_log.py:265 INFO * GitHub token... >>> * GitHub token...== 2020-03-06 07:37:29,261 github.py:1816 WARNING Failed >>> to obtain GitHub token for tardigradus >>> Use the following procedure to install a GitHub token in your keyring: >>> $ python -c 'import getpass, keyring; keyring.set_password("github_token", >>> "tardigradus", getpass.getpass())' >>> == 2020-03-06 07:37:29,261 build_log.py:265 INFO (no token found) => FAIL >>> (no token found) => FAIL >>> >>> The string 'fetch_github_token' doesn't occur in the log file. >>> >>> Is that any help? >>> >>> Cheers, >>> >>> Loris >>> >>> Kenneth Hoste <[email protected]> writes: >>> >>>> Dear Loris, >>>> >>>> That's... weird. >>>> >>>> Any trace of useful information in the log file? >>>> >>>> To make it easier and include more information, you can try running: >>>> >>>> eb --github-user tardigradus --check-github --debug -l > eb.log >>>> >>>> And then consult eb.log for relevant warning messages. >>>> >>>> There should be warning log messages from the 'fetch_github_token' >>>> function that >>>> tries to obtain the token that may point out the problem. >>>> >>>> >>>> regards, >>>> >>>> Kenneth >>>> >>>> PS: Make sure you don't accidentally share your token (but I noticed you're >>>> already paying attention to that, since xyz are not valid characters in a >>>> token >>>> ;) ). >>>> >>>> >>>> On 05/03/2020 10:49, Loris Bennett wrote: >>>>> Hi, >>>>> >>>>> I'm trying to set up Github integration. I have created a token and >>>>> installed it: >>>>> >>>>> [build@admin ~]$ eb --github-user tardigradus --install-github-token >>>>> == temporary log file in case of crash >>>>> /tmp/eb-KX8ZR3/easybuild-mN7UXX.log >>>>> Token: >>>>> Validating token... >>>>> Token seems to be valid, installing it. >>>>> Token 'xyz..123' installed! >>>>> >>>>> However, if I check the status via 'eb', I get: >>>>> >>>>> [build@admin ~]$ eb --github-user tardigradus --check-github >>>>> == temporary log file in case of crash >>>>> /tmp/eb-vB97DT/easybuild-hmtD38.log >>>>> >>>>> Checking status of GitHub integration... >>>>> >>>>> Making sure we're online...OK >>>>> >>>>> * GitHub user...tardigradus => OK >>>>> * GitHub token...(no token found) => FAIL >>>>> >>>>> What am doing wrong? >>>>> >>>>> Cheers, >>>>> >>>>> Loris >>>>> >>>> >> -- >> Dr. Loris Bennett (Mr.) >> ZEDAT, Freie Universität Berlin Email [email protected] > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
