{"push_id":988048229,"size":1,"distinct_size":1,"ref":"refs/heads/9.0","head":"f09edcddf9ab81bf71c82e5495e989b9ad8a1101","before":"30cf60a659ec1801e52427481b6a673ba2c1d0ee","commits":[{"sha":"f09edcddf9ab81bf71c82e5495e989b9ad8a1101","author":{"email":"d670d44c3ca8bd4cd53a3b09f8bf8fc35e4843cc@openerp.com","name":"Olivier Dony"},"message":"[FIX] assets: empty compiled assets handling\n\ntl;dr: accept both `None` and empty ('') results as\n       cache hits, then double-check that the file_size\n       is really 0\n\nA. Valid empty files\n\nWhen a LESS file compiles to an empty result\n(e.g. `variables.less`), do not treat the empty file\nas a cache miss. Those are valid because file_size == 0.\nNote: empty files are not stored in the attachment\nfilestore and return a null (None) `datas` when read\nfrom the database.\n\nB. Invalid empty files\n\nUnder some circumstances (e.g. damaged filestore,\nrace conditions during deletion, etc.), cached\ncompiled assets may be deleted in the underlying\nattachment filestore, while still present in the\ntable. The filestore implementation returns an\nempty file ('') when they are later accessed.\nThose can be considered **invalid**\nbecause the expected file_size is > 0.","distinct":true,"url":"https://api.github.com/repos/odoo/odoo/commits/f09edcddf9ab81bf71c82e5495e989b9ad8a1101"}]}