stuff related to https://forge.softwareheritage.org/diffusion/DSTO/
Wed, Feb 20
Tue, Feb 19
Thu, Feb 14
Tue, Feb 12
Mon, Feb 11
Fri, Feb 1
@ardumont These timeouts are either caused by the high CPU usage of swh-storage, or an unrelated issue.
Thu, Jan 31
@ardumont These timeouts are either a cause of the high CPU usage of swh-storage, or an unrelated issue.
There now remains errors :
- directly related to indexers (bad input) so indexer fails
- Sometimes it's the indexer's api call to the indexer storage that fails. I've created a dashboard to see those errors 
To exercise my hypothesis, i've increased that timeout to 1second for storage0.euwest.azure.
So far so good.
oh, i think i know...  We have a timeout of some endpoint...
Once in a while, an indexer worker crashes with the following error:
Tue, Jan 29
I agree we must be careful with not bloating swh.core, but the current subject, it really makes sense to me to put this basic db access wrapper as a core functionality.
Thu, Jan 24
Jan 21 2019
The object storage doesn't have content names, so it cannot address this feature as stated.