framecpp_verify and framecpp_checksum give false failures on file checksums
It appears that for frames that are greater than 4G in length, the framecpp CRC checksum code calculates a wrong value.
We'll be having a short maintenance tomorrow, 9 September 2025, starting around 9am PDT to apply a couple of configuration changes recommended by GitLab support following the slowdowns experienced last week. Whilst not yet a solution this should provide better performance for background jobs and potentially provide more information in the logs if/when the slowdowns start happening again. I expect the downtime to be brief, as in only a few minutes...
It appears that for frames that are greater than 4G in length, the framecpp CRC checksum code calculates a wrong value.