Most of the requests to the kernel in the latest main branch (v2.5.3) throw with these cloudflare errors:
The script will never generate a response
Worker exceeded CPU time limit
That is why the production kernel was downgraded to v2.5.2 (in particular this commit) which works as expected.
When the Devcon conference ends (15th November) we should:
Release a new kernel version
Set the newly released kernel version as the "latest" in cloudflare dashboard of the ubiquity-os-kernel-main worker
Check if the errors still persist
If the errors are still there then find the root cause and fix it
Possible solution (originally posted by gentlementlegen):
was digging into this a bit, sadly works fine locally. I also syumbled upon this thread https://github.com/cloudflare/workerd/issues/210
Another theory is that recently we made all plugins being called simultaneously, which maybe hits a cloudflare limit or doesn't resolve properly, which would not be an issue when run locally.
https://github.com/ubiquity-os/ubiquity-os-kernel/blob/6037f76c1ec2bad7abf34b6971b477b1109439c9/src/github/handlers/index.ts#L72
maybe worth a try to use allSettled or move it back to synchronous and see if that clears the issue.
Most of the requests to the kernel in the latest
main
branch (v2.5.3) throw with these cloudflare errors:The script will never generate a response
Worker exceeded CPU time limit
That is why the production kernel was downgraded to v2.5.2 (in particular this commit) which works as expected.
When the Devcon conference ends (15th November) we should:
ubiquity-os-kernel-main
workerPossible solution (originally posted by
gentlementlegen
):