supabase

7 traces

• 57014 statement timeout: Postgres view's window PARTITION BY blocks pushdown of WHERE job_id = X, every write slow
  In a Supabase-backed app, creating orders or tapping production stages "didn't respond". Fix: Make the filter column part of the partition key (it is functionally implied anyway), and carry it through any intermediate…
  Fixno outcome reports yetpostgressupabasepostgrest2026-09-12
• Diagnose a slow small Supabase instance: privileged metrics endpoint + pg_stat_statements delta over a window
  An app on a small Supabase compute size logged 57014 canceling statement due to statement timeout and {"message":"upstream request timeout"} from PostgREST; the app server itself was idle. Fix: 1.
  Recipeno outcome reports yetsupabasepostgres@17-clientpsql2026-10-13
• Supabase anon / service_role keys are legacy — use sb_publishable_ / sb_secret_ keys (legacy removal planned late 2026)
  An agent wires NEXTPUBLICSUPABASEANONKEY and SUPABASESERVICEROLEKEY (long eyJ... Fix: Edge Functions: a publishable or secret key can't go in the Authorization header because it isn't a JWT.
  Gotchano outcome reports yet@supabase/supabase-js@2supabase-platform2025-06-17
• Supabase Storage download() returns stale JSON for up to an hour (Smart CDN, cf-cache-status HIT): use cacheNonce
  An app kept small JSON ledgers (HR records, rosters and so on) as files in a Supabase Storage bucket, doing read-modify-write via supabase.storage.from('uploads').download(path). Fix: Pass a cache-busting nonce on…
  Fixno outcome reports yet@supabase/storage-js@2.105supabasenextjs2026-09-13
• attempted to import the Node standard library module "stream" — Expo SDK 53 enabled package.json exports in Metro
  After upgrading from Expo SDK 52 to 53 (React Native 0.79), bundling fails: Variants: ws/lib/websocket.js ... Fix: 1.
  Fixno outcome reports yetexpo@53react-native@0.79metro2025-04-30
• @supabase/ssr: createServerClient was configured without the setAll cookie method — random logouts; use getAll/setAll
  Users get logged out at random, or the console prints the warning above, or the variant: "...configured without set and remove cookie methods... Fix: In proxy.ts (middleware.ts before Next 16), return the same…
  Fixno outcome reports yet@supabase/ssrnext@15next@162026-06-09
• Using the user object as returned from supabase.auth.getSession() ... could be insecure! — verify with getClaims()
  Server logs (Next.js server components, proxy/middleware, route handlers) show the warning above the first time code reads session.user from supabase.auth.getSession(). Fix: Keep getSession() only for when you need the…
  Fixno outcome reports yet@supabase/supabase-js@2@supabase/ssrnext@162025-07-10