andk
Improve wording of the email sent when indexing fails due to DB lock timeout
When the indexer fails due to a DB lock timeout, we send an email to the uploader.
We could improve the email by:
- mentioning that this sometimes happens
- tell them that they can force a reindex
- tell them how they can check what entries are in the index for their dist
Email that Neil sent me would be an excellent starting point, since it told me everything I needed to know.
When you get an error like this, it’s best to wait a bit and see whether your release got indexed. Looking in the CPAN Index, I see:
Carp::Assert::More 2.000001 P/PE/PETDANCE/Carp-Assert-More-2.0.1.tar.gz
So the index was updated with your release, so everything’s ok.
If had seen the previous release still listed in the index, you can ask PAUSE to retry the indexing: in the left sidebar you’ll see "Force Reindexing". If you select that, you can pick a tarball and then hit "Reindex". Usually that will do the trick. If not, then contact the PAUSE admins.
