sqlite3 errors or Couldn't Find That Page

[Tidynator]

Good morning

Very often, upon consulting the documentation of a gem, coming from rubygems.org, I either get an error
SQLite3::CorruptException: database disk image is malformed

or just the message “Couldn't Find That Page”. The situation is each time identical, the difference between the reactions of your application are insignificant, as – often enough – reloading the page – be it by jumping on the reload button like an ape – produces the sought content.
Sometimes not.

Maybe you can catch an Exception somewhere, add some condition-testing or what do I know... and show something more authentic? Like: “For the time etc.” or “Please come back later” or “Please jump on the reload button like an ape”.

Thank you

Edit: The best, for now (“We can, but we cannot”):
https://pic.infini.fr/bH24WfFj/lScFreKr.png

[hernanat]

perhaps also connected, I've been getting a lot of these lately:

[hernanat]

I'd love to help figure out these issues but I can't even get the application running locally (following the README). @lsegal any tips?

[lsegal]

I'd love to help figure out these issues but I can't even get the application running locally (following the README). @lsegal any tips?

If you're looking at helping us identify production issues the easiest way to get started would be to run the app locally. The Docker instructions should work (you may need to adjust replicas if you're not using swarm to loadbalance instances), and they represent how we deploy to rubydoc.info. You can actually see the scripts we use in scripts/start.sh

[skatkov]

@lsegal would it be possible to introduce error catcher to production server? There is probably something free for open source projects... maybe https://honeybadger.io?

It would tremendously help understand how often these issues are happening and their source.