While I was in Heidelberg last month tackling material on the DCLP board, Hugh undertook some system maintenance, which concluded with a re-index. One consequence of that work is that, on the morning of June 9, most of the material on the DCLP board had been corrupted where previously it had not: attempts to access DCLP Text resulted in a short pause and in being redirected to my dashboard, with the red error flag: "Error retrieving file content from repository. This error has been logged for review by an administrator." The DDB board was not similarly impacted.
Since then, whatever went wrong has for the most part been remedied (maybe Hugh's maintenance hadn't finished?) Where corruption recurred (see list below), Ryan's Recover Branch button successfully retrieved the files. No harm, no foul, largely speaking. But because DCLP has a bit of history of files becoming corrupted, and because in this case it was evidently correlated to system maintenance that included a re-index, I'm ticketing it for your attention. Maybe the logs for June 9 2023 will reveal something?
The following are files that continued to be corrupted, but whose Git branch was recovered via Ryan's automated process:
While I was in Heidelberg last month tackling material on the DCLP board, Hugh undertook some system maintenance, which concluded with a re-index. One consequence of that work is that, on the morning of June 9, most of the material on the DCLP board had been corrupted where previously it had not: attempts to access
DCLP Textresulted in a short pause and in being redirected to my dashboard, with the red error flag: "Error retrieving file content from repository. This error has been logged for review by an administrator." The DDB board was not similarly impacted.Since then, whatever went wrong has for the most part been remedied (maybe Hugh's maintenance hadn't finished?) Where corruption recurred (see list below), Ryan's
Recover Branchbutton successfully retrieved the files. No harm, no foul, largely speaking. But because DCLP has a bit of history of files becoming corrupted, and because in this case it was evidently correlated to system maintenance that included a re-index, I'm ticketing it for your attention. Maybe the logs for June 9 2023 will reveal something?The following are files that continued to be corrupted, but whose Git branch was recovered via Ryan's automated process:
https://papyri.info/editor/publications/128822 https://papyri.info/editor/publications/120329 https://papyri.info/editor/publications/120201 https://papyri.info/editor/publications/118763 https://papyri.info/editor/publications/116873 https://papyri.info/editor/publications/116326 https://papyri.info/editor/publications/112229