But if I "hg clone" from forge-migrate4 and push it into a sandbox repo, it all is fine. Also, cloning directly from the original classic repo like the migration script does worked fine:
The commits' file diffs, and tree objects differ between local and production. They seem more correct locally, but still not all correct. Commit tip is:
new tests cover the broken functionality; hard to duplicate manually
to fix the data in production, we'll run the above commands. Apr 1 is used because the regression happened then, with commit f461c6 which removed __repr__
you can test the above commands by importing a repo of any type, then deleting some of the repo_objects (e.g. above some _id) and then running the refresh command.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure what's going on. If I clone the repo within production Allura, the problem persists: https://sourceforge.net/u/brondsem/test-hg/
But if I "hg clone" from forge-migrate4 and push it into a sandbox repo, it all is fine. Also, cloning directly from the original classic repo like the migration script does worked fine:
The commits' file diffs, and tree objects differ between local and production. They seem more correct locally, but still not all correct. Commit tip is:
db.repo_object.find({object_id: '5f4c74506c370494203e0371431a34d5b1ee4b3c'})
I can't find where Commit.tree is set for Hg. refresh_commit's fake_tree seems plausible, but doesn't appear to run when importing a new tree
forge:db/1942
__repr__