2024-07-25

[kltm]

• [x] Send reminder email to go-consortium mailing list
• [x] Run noctua-models-migration pipeline for (@vanaukenk) (automated to day before) to get report
  http://skyhook.berkeleybop.org/noctua-models-migrations/reports/
• [x] Refresh minerva code with latest from minerva master
• [x] Run replaced_by term update on blazegraph (@vanaukenk)
• [x] Cycle minerva to get latest ontology
• [x] Update NEO
• [x] Prep ticket for next outage

[kltm]

Noting that this will be a long-running outage.

[kltm]

@vanaukenk Some changes found in migration.

[vanaukenk]

Noting that all of the changes in the diff are consistent with recent ontology merges.

[kltm]

Before closing this out, it's worth noting some oddities.

When starting the outage, it was noted that 477 commits had not been pushed due to the origin being ahead. Thinking about it, given that the last outage was suspended halfway through, it's possible that the "local" recreation and "settling" may have occurred, but not the migration. This seems consistent with the conflicts found in the models, as they were mostly dates and anonymous nodes. After manual examination, we went ahead with the current state of minerva on production's disk as the correct state, overlayed it, refreshed, and proceeded with the outage as normal. (Thank you @vanaukenk.)

The conflicted state of the repo was pushed into github during this examination by the automated process, so that is preserved for future examination (and/or surprises!) as well.

I'd also note that the github session for pushing seems to have been expired as well, which may have been a contributing factor.