You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release summary data (CPAN::Testers::Schema::Result::Release) has many rows with incorrect relationships to the uploads table (via the uploadid column). We should write a runnable module (using Beam::Runnable) that check to see that all of the dist/version information in this table is correct to the uploadid it is linked to.
If the data is incorrect, the script should fix it, but only if there is only one possible dist/version in the uploads table (see #16). In either case, the script should print out the offending row and either say that it has fixed it (and write what uploadid it fixed it to) or say that it could not be fixed automatically (and say which uploadids were available, and print the upload rows).
This process should be configured in etc/container/schema.yml and run via cron on a nightly basis.
The text was updated successfully, but these errors were encountered:
The release summary data (CPAN::Testers::Schema::Result::Release) has many rows with incorrect relationships to the uploads table (via the
uploadid
column). We should write a runnable module (using Beam::Runnable) that check to see that all of the dist/version information in this table is correct to the uploadid it is linked to.If the data is incorrect, the script should fix it, but only if there is only one possible dist/version in the uploads table (see #16). In either case, the script should print out the offending row and either say that it has fixed it (and write what uploadid it fixed it to) or say that it could not be fixed automatically (and say which uploadids were available, and print the upload rows).
This process should be configured in
etc/container/schema.yml
and run via cron on a nightly basis.The text was updated successfully, but these errors were encountered: