checkout_externals hangs on subversion call on new machine

[mnlevy1981]

Summary of Issue:

I just got access to a new machine and checkout_externals -v from cesm2.2.0 hung at

Processing externals description file : Externals_CAM.cfg
Checking out externals:

---
        -,  -->
    svn checkout --quiet https://svn-ccsm-models.cgd.ucar.edu/tools/proc_atm/chem_proc/release_tags/chem_proc5_0_04 /nfspool-0/home/mnlevy/codes/CESM/cesm2.2.0/components/cam/chem_proc

When I finally ^Ced out and manually ran the checkout, I was greeted with

$ svn co https://svn-ccsm-models.cgd.ucar.edu/tools/proc_atm/chem_proc/release_tags/chem_proc5_0_04 chem_proc
Error validating server certificate for 'https://svn-ccsm-models.cgd.ucar.edu:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.cgd.ucar.edu
 - Valid: from Mon, 18 Nov 2019 00:00:00 GMT until Wed, 17 Nov 2021 23:59:59 GMT
 - Issuer: InCommon, Internet2, Ann Arbor, MI, US
 - Fingerprint: 1a:41:6e:31:c5:f7:99:dd:b7:72:cc:c6:30:b9:e1:c7:90:82:d3:c8
(R)eject, accept (t)emporarily or accept (p)ermanently?

After permanently accepting it, I could re-run checkout_externals with no issues.

Expected behavior and actual behavior:

It would be nice if checkout_externals could forward this prompt from subversion to stdout, but instead it just hangs.

Steps to reproduce the problem (should include model description file(s) or link to publi c repository):

1. Find a machine that has never checked out a subversion repository from https://svn-ccsm-models.cgd.ucar.edu
2. Clone cesm2.2.0 from https://github.com/ESCOMP/cesm
3. Run manage_externals/checkout_externals -v

What is the changeset ID of the code, and the machine you are using:

I think this is manic-v1.1.8? It's whatever is in CESM 2.2.0, and the machine is a cluster at UC-Irvine

have you modified the code? If so, it must be committed and available for testing:

no

Screen output or log file showing the error message and context:

I think this is all captured above.

[billsacks]

I believe this is the same as #115 , which I closed as a wontfix. It looks like you are experiencing behavior similar to the initial report, whereas my attempts to reproduce it (by temporarily renaming ~/.subversion) led to the message being forwarded to the terminal, as you want. I'm not sure what leads to this different behavior.

If you let it go (without ^C), do you at least get the message that it may be hanging (as noted in #115 )? If so, is that possibly enough for now?