Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloudflare error: The script will never generate a response #195

Closed
rndquu opened this issue Nov 12, 2024 · 1 comment · Fixed by #199
Closed

Cloudflare error: The script will never generate a response #195

rndquu opened this issue Nov 12, 2024 · 1 comment · Fixed by #199
Assignees

Comments

@rndquu
Copy link
Member

rndquu commented Nov 12, 2024

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:

  1. Release a new kernel version
  2. Set the newly released kernel version as the "latest" in cloudflare dashboard of the ubiquity-os-kernel-main worker
  3. Check if the errors still persist
  4. 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.
Copy link

A new workroom has been created for this task. Join chat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant