search

ubiquity-os / ubiquity-os-kernel

1 stars 19 forks source link

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

Open gentlementlegen opened 2 weeks ago

gentlementlegen commented 2 weeks ago 
          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 https://github.com/ubiquity-os-marketplace/command-ask/issues/19#issuecomment-2440529657