No need to filter out revisions as well, this is already handled elsewhere.
Along with D7028, this resolves T3884.
Differential D7029
Filter out extids targeting non-existing releases vlorentz on Jan 24 2022, 6:04 PM. Authored by
Details
No need to filter out revisions as well, this is already handled elsewhere. Along with D7028, this resolves T3884.
Diff Detail
Event TimelineComment Actions Build is green Patch application report for D7029 (id=25479)Rebasing onto 78b2e9f7f4... Current branch diff-target is up to date. Changes applied before testcommit dddd7d49262d6f553ecf8c898a3415fd1bdf71c3 Author: Valentin Lorentz <vlorentz@softwareheritage.org> Date: Mon Jan 24 18:03:57 2022 +0100 Filter out extids targeting non-existing releases No need to filter out revisions as well, this is already handled elsewhere. Along with D7028, this resolves T3884. See https://jenkins.softwareheritage.org/job/DLDBASE/job/tests-on-diff/687/ for more details. Comment Actions I wonder if that'd be worth a warning. May end up being a bit noisy though. Or, in other words: are there any usecases where inserting an extid pointing to an object we don't have in the archive makes sense? Comment Actions Sentry recorded only two occurences so far, so it shouldn't be too noisy.
I don't see any, especially not in package loaders Comment Actions Build is green Patch application report for D7029 (id=25504)Rebasing onto 78b2e9f7f4... Current branch diff-target is up to date. Changes applied before testcommit 4718713b9ae0c7fedefd82d0d5944c4871943065 Author: Valentin Lorentz <vlorentz@softwareheritage.org> Date: Mon Jan 24 18:03:57 2022 +0100 Filter out extids targeting non-existing releases No need to filter out revisions as well, this is already handled elsewhere. Along with D7028, this resolves T3884. See https://jenkins.softwareheritage.org/job/DLDBASE/job/tests-on-diff/688/ for more details. |