@dorothyr Yeah, I had all the boxes checked in the window. And I just tried a fresh checkout with a different file and I get the same issue (see attached screenshot).
Okay. Find attached a trace output. I think I did it right? But let me know if not. I opened tkrev and pressed the "Branch" button for cvsxdiff. The warning popup came after: [::cvs_branchlog::2::cvs_sort_it_all_out] ENTER
Hmm. How do you enter trace mode? I don't see a command line option. Also: one thing I forgot. We access our CVS server via ssh (CVS_RSH=ssh) and we have to use a custom port (via .ssh/config). Could that cause issues?
@dorothyr Please find attached the cvsxdiff,v file. Hopefullly it helps you figure out my oddity.
@dorothyr Okay. I'll work with the person with access to try and get it. Note: I did try the usual "let's see if ChatGPT" can help and I'm not sure our robot friend knows TCL that well. :)
@dorothyr Zombie thread activate! (Sorry about that.) Back in 2020, we sort of "moved full in to Git" and so my support requests (from users) for CVS stopped. However, recently, some old CVS code was revived and people asked about tkcvs. 2020 was a few OSs ago, so I installed tkrev anew (9.5) and decided to try again. And so I tried again with the same file as above. Good news, doesn't crash. Bad news, doesn't work. I get a popup saying: TkRev Warning! Log empty. Check error status of cvs log command...
This is an odd one discovered by a user of some data some colleagues make. Note: my guess is this isn't actually an issue in NCO, but probably a difference in HDF5/netCDF, but we want to make sure. Namely, we recently had an OS upgrade on our cluster to SLES15 and this forced quite a few older running models to need to move to newer compilers, etc. And in that, newer HDF5/netCDF/NCO because, well, I couldn't figure out how to build 10-year old libraries with recent compilers. So, essentially, what...
Thanks for finding it! I figured it was some group thing as I don't often see them in my work, but others have files with them. I'll try and do a snapshot if I have a chance, but my guess is you might release before then given how busy things are for me now.