CSimultaneous Open Connections are measured from the top-level request, meaning any connections open from Workers sharing resources (for example, Workers triggered via Service bindings) will share the simultaneous open connection limit.
RC
III
B
O
ScheduleContext seem to be missing kv fieldO
F
A
MWorkerEntrypoint methods? I'm trying to avoid having to pass context variable into every method in the WorkerEntrypoint.
W
J
tower_http::trace::TraceLayer to a worker somehow? In normal non-wasm axum I'd just add .layer(ServiceBuilder::new().trace_for_http()), but when running with cloudflare I get the unhelpful (seemingly impossible to debug) error:J
T
TTIITTTT GitHub already has access to sensitive data so I think it's better to centralise secrets there
W
SS
L
E
C
NN
ScheduleContextWorkerEntrypointWorkerEntrypointtower_http::trace::TraceLayer.layer(ServiceBuilder::new().trace_for_http())✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished. - name: Deploy worker
uses: cloudflare/wrangler-action@v3
with:
secrets: |
WORKER_SECRET
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
wranglerVersion: "3.78.4"
env:
WORKER_SECRET: ${{ secrets.WORKER_SECRET_FROM_GITHUB_SECRETS }}
CDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / workers-and-pages-help