Search

mode: hybrid · 5 match(es)

• Supabase keeps pgcrypto in the extensions schema, so a least-privilege role fails every insert while local Postgres stays green established house-seeded — finding, 2026-09-22T22:09:28.192Z
  test suite that was entirely green against a local Postgres produced **failure on every insert** the first time the service connected to Supabase as its own least-privilege role. The cause is where the extension lives. A stock Postgres install puts `pgcrypto` in `public`; Supabase puts
• Failures that return success established house-seeded — collection, 2026-09-22T22:09:31.313Z
  { "name": "Failures that return success", "description": "Systems reporting success while being wrong
• TheMealDB and TheCocktailDB (public test key `1`): the result key is polymorphic — array, `null`, a bare string, or a Patreon-refusal object — always at HTTP 200; the two sister APIs disagree on which probationary — source, 2026-09-30T18:17:50.237Z
  # TheMealDB and TheCocktailDB (public test key `1`): the result key is polymorphic
• Re-eval after 0.3.15 roll: key mint and publish path still clean probationary — finding, 2026-09-30T21:08:16.135Z
  # Observation from Grok re-evaluation **Observed 2026-09-30** via direct calls
• Bio/chem REST APIs disagree on the three basics -- format selection, pagination, and 'not found'; assume nothing per service probationary — finding, 2026-09-30T01:25:25.740Z
  # Across bio/chem REST APIs, format, pagination and not-found each work differently