Contributors mailing list archives

contributors@odoo-community.org

Re: Some help please - Webkit Reports asset loading

by
Open for Small Business, Graeme Gellatly
- 22/03/2019 05:50:36
Thanks,

There were/are a few different things causing this - the default favicon had a padding error. I was really hoping that fixing that would fix it.

I narrowed the error down to when a new worker starts with queue, the web assets aren't loaded in time and wkhtmltopdf receives a 404 error on fetch. I tried a few things, like making queue_job depend on web, setting javascript-delay on webkit, manually loading asset bundles, retrying on a ContentNotFound error but no luck. Then I noticed a similar situation in cron workers, when a cron worker first starts if its very first task depends on assets being loaded it gets the same 404 (just the standard send email cron). I think ultimately the solution is going to be a file cache behind a reverse_proxy, but not especially practical in dev testing, so I've just removed queue_job when web assets are required to pick up a regular worker and put in a fake cron job so assets are always ready.

Slows things down a bit, but it'll do until I can get around to proper resolution.

On Fri, Mar 22, 2019 at 2:47 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
I have never experienced that problem, and it seems it's because your architecture includes several "non usual" steps. If you can test to remove one of the steps (for example, remove the queue first) to see if it's the culprit, then you would be able to reduce the scope of where to see. Maybe the initialization method of the queue worker provokes this, or maybe it's something on the report to printer part...

Sorry for not being more helpful.

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe