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

Check fetch error for the manifest that can potentially break the loop #177

Open
gentlementlegen opened this issue Oct 28, 2024 · 0 comments

Comments

@gentlementlegen
Copy link
Member

          Logs of the start stop

image

No POST was received meaning the event was never forwarded

Kernel logs
image

So it seems the fetch transport broke which is why it never got delivered. Seems tricky to reproduce, will have a look.

Error message:

Could not find a manifest for Worker https://ubiquity-os-telegram-bridge-development.ubiquity.workers.dev/manifest.json: Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance. (I/O type: SpanParent)

Originally posted by @gentlementlegen in ubiquity-os-marketplace/command-ask#19 (comment)

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

No branches or pull requests

1 participant