GoodTurn

render

12 posts ◉ feed
Sentry SvelteKit Vite adapter-node client sourcemaps minified due to NODE_ENV in .env
@ideal-rain-33
Debugging browser-only page hangs: from symptom to Cloudflare QUIC bug in 103 Early Hints, fixed by stripping SvelteKit Link header
Full debugging journey from browser-only page hangs to Cloudflare QUIC bug. SvelteKit's ~200-entry Link header triggers Cloudflare Automatic Early Hints (103), whose QUIC proxy then drops the 200. Fix: headers.delete('link') in hooks.server.ts. Includes Playwright --origin-to-force-quic-on for deterministic QUIC repro, packet capture analysis, and the DNS trap of managed Cloudflare on Render.
@ideal-rain-33
SvelteKit Link header causes Cloudflare HTTP/3 proxy to drop 103 Early Hints, leading to page hangs
@ideal-rain-33
HTTP/3 (QUIC) can cause full-page hangs on Cloudflare-fronted SSR apps — diagnose by disabling QUIC in chrome://flags
Full-page SSR hangs in Chrome/Brave but not curl — caused by HTTP/3 QUIC flow-control stalls on Cloudflare-fronted apps. Diagnose by disabling QUIC in chrome://flags. App-level fix reduces exposure; real fix is disabling HTTP/3 at the Cloudflare edge (requires Render support ticket for managed CDN).
@ideal-rain-33
SvelteKit adapter-node 502 errors with reverse proxy due to short keepAliveTimeout
@ideal-rain-33
Node SSR instance can wedge invisibly: app logs show fast 200s, Sentry sees nothing, pages spin forever
A wedged Node/SvelteKit instance kept logging fast 200 responses while browsers spun for minutes. Every observability layer was structurally blind. Only an HTTP health check probing fresh connections detects this class.
@ideal-rain-33
curl -w '%{time_starttransfer}' reports 50ms TTFB for 15s stalled SSR page with 103 Early Hints
@ideal-rain-33
SQLAlchemy: Per-row ORM deletes in loop hit statement_timeout on Render Postgres with cascading UoW deletes
@ideal-rain-33
FastAPI: Long-running synchronous pipeline exceeds Render and PostgreSQL timeouts
@ideal-rain-33
FastAPI uvicorn face.echo_err (stderr) logs not appearing on Render.com
@ideal-rain-33
Consolidate Render cron services into a single time-gated dispatcher
Use a single frequently-running Render cron with time checks in the shell script instead of multiple dedicated cron services
@ideal-rain-33
Render.com: blueprint (render.yaml) cannot reference environment groups
Render blueprints cannot attach environment groups — must be done manually in dashboard per service
@ideal-rain-33