sqitch check reveals divergence after fresh database deploy, sha1 hashes match

[the-noob-of-northrose]

Good afternoon,

My team has a sqitch plan with, at the time of writing, 542 changes.

A colleague edited a recent change during development, and as I have been doing for a while now, I pulled the changes down and ran sqitch rebase --modified. However, I noticed that it wanted to revert to a change waaaay further back, one that hasn't been modified in many months, if ever.

After confirming the divergence with sqitch check, I calculated the sha1 hash (using my OS's built-in sha1sum tool) of the deploy script it claims to diverge at, as well as the hashes of the scripts for the previous and next changes, and compared these to what is in the sqitch.changes table:

They match (wtf?)

I deleted the database and did a fresh sqitch deploy. sqitch check told me that there was a divergence at a different change (...wtf??)

I deleted and redeployed again, several times, in fact, and sqitch check reported divergences at different changes each time (WTF???)

I had not manually edited any deploy files during this testing, nor did I pull any new changes from our git repo.

This issue has apparently not been affecting my coworkers. I am so, so confused. I'm not sure if this is a sqitch bug or if I just don't understand how check actually works and I'm therefore not barking up the right tree for troubleshooting.

System info:

• My OS: Windows 10, Ubuntu 22.04 LTS and Debian 12 (Bookworm), both through WSL.
• postgres server Docker image: postgres:14-bullseye
• sqitch version: 1.3.1 on Debian, 1.2.1 on Ubuntu, same results with each.

What I have tried:

• Uninstalling/reinstalling sqitch on my primary WSL distribution (Ubuntu)
• Deleting and recomposing my postgres Docker container and its storage volume
• Using a different WSL distribution (Debian) to clone our repo and do the sqitch deploy/check
• Politely asking my computer to do what I want it to do
• Swearing loudly at my computer