- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 17 2021
Commits ingested before https://forge.softwareheritage.org/rDLDGfb03140e169f38f5ea0d64d81b524b4b967335f7 have an extra newline at the end of the mergetag header
Now most of the time can be spent in reading the actual mapping extids -> hgnode-id [1] to filter on something we already see.
Which does not change much from actual visits which already ended up in snapshot.
However that changes a lot for visits on forks where we can bypass already done work on those forks.
rebased patch
insert new entry in alphabetical order
Actually restarted the loader_oneshot which now makes usage of the latest v2.2.0 loader mercurial.
Build is green
Drop the hg to hg mapping, it's indeed not needed. I must have cross wired my mind and
fingers when testing that.
Build is green
Adapt according to suggestions to make code clearer! Thanks.
Thanks for the heads up, gonna simplify stuff then.
This one seems small enough to use as data for analyzing and possibly fixing the test:
Sep 14 04:09:01 worker17 python3[354854]: [2021-09-14 04:09:01,867: INFO/ForkPoolWorker-292] Load origin 'https://bitbucket.org/avnomad/d' with type 'hg' Sep 14 04:09:02 worker17 python3[354854]: [2021-09-14 04:09:02,826: ERROR/ForkPoolWorker-292] Loading failure, updating to `failed` status Traceback (most recent call last): File "/usr/lib/python3/dist-packages/swh/loader/core/loader.py", line 339, in load self.store_data() File "/usr/lib/python3/dist-packages/swh/loader/mercurial/from_disk.py", line 397, in store_data target = self.get_revision_id_from_hg_nodeid(node_id) File "/usr/lib/python3/dist-packages/swh/loader/mercurial/from_disk.py", line 471, in get_revision_id_from_hg_nodeid assert len(from_storage) == 1, msg % (hg_nodeid.hex(), len(from_storage)) AssertionError: Expected 1 match from storage for hg node '38663535643238346139643464376432313166303463626336373865396632313562333034343034', got 0 Sep 14 04:09:03 worker17 python3[354854]: [2021-09-14 04:09:03,137: INFO/ForkPoolWorker-292] Task swh.loader.mercurial.tasks.LoadMercurial[fd077098-7779-4633-805b-f0cb0ad85b2a] succeeded in 1.9395398199558258s: {'status': 'failed'}
The hg-git type are served as regular Mercurial repository. So they can be listed as Mercurial repository safely
Another run in on a large repository (which cannot finish, the error is independent
though) [1]
Packaged within the v0.37 version.
Deployed both in staging and production.
Deployed on staging and everything looked good.
So deployed on production as well.
Looks good to me !
Sep 16 2021
Two other sources of mismatched checksums:
Heads up, it seems the main issues mentioned above have subsided.
It's still ongoing but the tendency seem to go the right way.