Closed WValenti closed 4 months ago
Oh, I also tested (with a DIVER search) almost all other variables with ambiguous dates, and everything worked.
Doesn't happen on DIVER. The two entries are identical other than the table changes from DATABASE_EDIT 60, and, I assume corresponding code.
DATABASE_EDIT 60 was why this was coming up, after a fashion - those changes were in already but the corresponding handling code in diverweb was not yet deployed thereon. This has now been addressed, and the bug is no longer reproducible.
Simply searching for "i20480" gets a crash on grace:
Jo thought (while sick) that this was due to a top_values problem, but I directly UPDATEd both top_values and max_value to legit values from other variables in SVVFHVs, and it made no difference in the crash when re-invoked. I have put top_values back, but left max_value (it's UUUU instead of 2024).