ps-temp-hack-for-aggregate Temporarily make fetch always try aggregate if content is ni…

We get a lot of 406 errors from travis-api V2 when trying to fetch log
and I tracked it down to be a case when the remote log returns a nil
content (the error is wrong and it should be 404, but that's another
matter). This might happen when a log in the database has a NULL
content, but aggregated_at is still for some reason set to a value.

This commit is a hack in a way that if the diagnosis is right, we should
fix it wherever the aggregated_at is wrongly set with content still
being null. But it seems like the easiest solution at the moment.

Piotr Sarnacki avatar Piotr Sarnacki

Push event #1576 passed

  • Ran for
  • Total time