Expose and attest maxRetries:0 for authenticated Worker version uploads
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- api, backend-api-design
Direzione di ricerca
The issue names the authenticated Cloudflare MCP connection and Worker version-upload endpoint, but no source files, tests, or entry points. Start by locating the upload endpoint and tracing the complete outbound request path, including authentication and retry middleware. Done means a supported per-call maxRetries: 0 invocation and immutable deployed-build evidence that tests show at most one attempt for the specified failures.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
Strict single-attempt Worker version uploads cannot be safely admitted when the authenticated MCP connector or its outbound middleware may automatically resend a mutation after network errors or HTTP 429. Application-level no-retry logic alone does not establish an end-to-end one-attempt guarantee. Content-free HTTP status and numeric provider error codes are also needed to distinguish a rejection from an uncertain outcome.
Proposed Solution
Please provide a per-call, end-to-end single-attempt mode for Worker version uploads through the existing authenticated Cloudflare MCP connection.
Required behavior:
- Expose an enforceable
maxRetries: 0mode for the Worker version-upload endpoint. It must apply to the complete outbound path, including middleware, network-error and HTTP 429 handling, redirects, and any automatic replay after an authentication challenge. An uncertain outcome must return without resubmission. - Preserve sanitized HTTP status and numeric Cloudflare provider error codes, with an outbound-attempt count or equivalent nonsecret execution evidence. Do not include credentials, private headers, request bodies, or uploaded source in diagnostics.
- Identify the immutable build/version actually deployed behind the existing connection and provide verification evidence for that implementation, covering connection interruption, timeouts, HTTP 429 and HTTP 401/403. An application-level no-retry loop or a source-only patch is insufficient if another layer can resend the mutation.
- Reuse the existing authenticated connection without credential disclosure, credential export, or credential changes.
A feature-request acknowledgement or merged source change alone is not evidence that this mode exists in the deployed connector. Please confirm whether a verified single-attempt mode is currently available, and the exact invocation and deployed-version attestation needed to use it.
Alternatives Considered
A wrapper that avoids its own retry loop cannot control retries inside the connector. This request seeks support in the existing authenticated connection, without another service or credential export.
Additional Context
Please supply the exact supported invocation and an immutable identifier for the connector build actually deployed behind the existing connection. Verification must cover every outbound layer and show at most one mutation attempt. A feature acknowledgement or source-only change is not deployed-capability attestation. No private account details, credentials, logs, or implementation artifacts are included.
- Lingua principale
- TypeScript
- Stelle
- 1k
- Fork
- 158
- Merge medio
- 1g 2h
- PR unite (30g)
- 60
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di cloudflare/mcp
-
[Connection guide] Claude CodeForse già presa @umeraamir69 l’ha presa 21 giorni fa. Apertaenhancement good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
cloudflare/mcp#39 · 6 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
cloudflare/mcp#389 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 40/100
cloudflare/mcp#388 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
cloudflare/mcp#386 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 44/100
cloudflare/mcp#385 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di cloudflare/mcp
Issue simili
-
area:tooling good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
interledger/publisher-tools#1007 ·
I maintainer di solito rispondono entro 1 giorno
-
priority/medium roadmap/v1.1.1 stakeholder/rapr type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
databrickslabs/ontos#1420 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
vercel-labs/just-bash#756 ·
I maintainer di solito rispondono entro 1 giorno
-
area: ci good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
interledger/web-monetization-extension#1555 ·
I maintainer di solito rispondono entro 1 giorno
-
🐞 bug 🧐 unconfirmed
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
Tencent/tdesign-vue-next#7056 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno