Closed billsacks closed 4 years ago
@jgfouca I'm always confused by these encoding issues - what's the proper fix for this?
File "/home/sacks/ctsm_code/ctsm/cime/scripts/Tools/../../scripts/lib/CIME/Servers/wget.py", line 53, in getfile logging.warning("wget failed with output: {} and errput {}\n".format(output.encode('utf-8'), errput.encode('utf-8'))) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 119: ordinal not in range(128)
Fix coming, we seem to still have a lot of encodes/decodes floating around CIME that are not at all needed.
OK, I pushed a fix directly to master (it was very minor change). I made changes many months ago that ensured that users would never have to encode stuff coming back from run_cmd(...), regardless of their python version. I thought I had grepped-through the code and cleaned-up all the places that were doing these unnecessary encodings, but I either missing the ones in wget.py or they got reintroduced somehow.
With cime5.8.17: I added some files to the svn inputdata repository from cheyenne, then ran a test suite on izumi. The first test to reach the check_input_data phase failed, leaving behind a 0-size file. TestStatus.log shows the following:
That was on Saturday. When I manually removed the file and then ran
./check_input_data --download
manually this morning, it downloaded the file successfully.I'm not sure if this is a bug in the scripts or if it was due to a temporary server glitch - or both - but the traceback suggests to me that maybe the error handling code is not quite right? I'm up and running now so this isn't critical for me, but I'm reporting this in case it indicates a problem that should be fixed.