syntaqxnpm installs on g1t's cloud runners stop failing with "network aborted". The upstream sometimes broke off in the middle of a tarball's body, after its headers had already been handed to the sandbox, so the retry added for failed requests couldn't help: npm got a truncated file and gave up. Now an answer to a request that can be sent again (a GET or HEAD with no body), of known length up to 8 MB and sent uncompressed, as package tarballs are, is read whole by the runner Worker before the sandbox gets it; one whose body breaks off is tried again, twice, and still failing becomes a 502 saying why, never a truncated answer. Larger answers and ones of unknown length stream as before. And the repository's installs open at most 8 connections at once rather than npm's 15, since each passes through the Worker and bursts of parallel downloads were when it happened.4ffd59cHistory
- ..
- agents
- chat
- customize
- folios
- people
- team
- actions-settings.tsx
- agents.tsx
- apps.tsx
- audit-export.ts
- audit.tsx
- billing.tsx
- chat-settings.tsx
- code-access.tsx
- code-overview.tsx
- context.tsx
- emoji.tsx
- gateway.tsx
- guardrails.tsx
- home-seen.ts
- home.tsx
- integrations-directory.tsx
- integrations.tsx
- layout.tsx
- member-invitations.tsx
- members.tsx
- memory.tsx
- moved.ts
- new.tsx
- overview.tsx
- package.tsx
- packages.tsx
- people.tsx
- permissions.tsx
- personal-access-tokens.tsx
- pins.ts
- projects.tsx
- repositories.tsx
- rules.tsx
- ruleset.tsx
- runners.tsx
- secrets.tsx
- security-bypass.tsx
- security-patterns.tsx
- security-settings.tsx
- security.tsx
- settings.tsx
- soon.tsx
- spend-pill.ts
- spend-receipt.tsx
- spend.tsx
- statement-csv.ts
- statement-entries.ts
- tab-soon.tsx
- team-new.tsx
- teams.tsx
- token-new.tsx
- token.tsx
- tokens.tsx
- usage.tsx
- webhooks.tsx
- workspace-overview.tsx