Trouble with GitHub proxy
Dev tooling8 posts from 2 people2d active+00 posts in the last 7 days, 0 the 7 days before (fading)
Posts per day
The posts behind it
8, newest firstStream DB proxy results with bounded batches and cancellationDeliver query results through gRPC without buffering the whole result or retaining database resources after a request ends. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** New proxy repository. ## Acceptance criteria - [ ] Send column...grafana/grafana · owensmallwoodOpen ↗Roll out the DB proxy and Usage Insights integration to productionProgressively enable the production consumer with explicit health and performance checks. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** deployment_tools, grafana-enterprise. ## Acceptance criteria - [ ] Promote the proxy and compatible...grafana/grafana · owensmallwoodOpen ↗Remove Usage Insights direct database access after proxy cutoverComplete the MVP by removing the consumer's direct database dependency after successful production cutover. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** deployment_tools, grafana-enterprise. ## Acceptance criteria - [ ] Remove obsolete...grafana/grafana · owensmallwoodOpen ↗Validate Usage Insights through the complete DB proxy pathVerify correctness, operational failure behavior, compatibility, and representative performance before production cutover. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** New proxy repository, grafana-enterprise, deployment_tools. ##...grafana/grafana · owensmallwoodOpen ↗Authenticate and authorize DB proxy requestsAdmit only the initial consumer through the existing CAP token-exchange and authlib flow. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** New proxy repository. ## Acceptance criteria - [ ] Validate signed access tokens, intended audience,...grafana/grafana · owensmallwoodOpen ↗Add DB proxy query observability and operational documentationMake every query attempt and its outcome observable, with monitoring and ownership sufficient for production operation. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** New proxy repository, deployment_tools. ## Acceptance criteria - [ ]...grafana/grafana · owensmallwoodOpen ↗Implement the DB proxy gRPC client and Go SQL driverExpose the proxy through database/sql so callers can retain their existing query-library behavior. Parent: https://github.com/grafana/grafana/issues/134293 **Implementation locations:** Client/driver location selected in issue 2. ## Acceptance criteria - [ ] Implement...grafana/grafana · owensmallwoodOpen ↗Proxy/middleware file trace (middleware.js.nft.json) includes unrelated Prisma native binaries never referenced by the compiled bundle...of this over-inclusive trace, **any Next.js 16 app that uses Prisma anywhere at all fails to deploy on Netlify**, even with a `proxy.ts` that has no database code whatsoever. Two independent refactors we tried - removing every direct and indirect Prisma import from `proxy.ts`'s...vercel/next.js · roji-tech1 repliesOpen ↗
Companies and products named
About this problem
Evidence
8 posts from 2 people in 2 places, about 4 a week over 14 days. Mostly on grafana/grafana, vercel/next.js. Tools named alongside: Grafana, AWS, Netlify, Prisma.
Frustration Frustration 1 of 3· Seen on GitHub issues
How it was grouped
Posts about GitHub with no known issue, sharing the word "proxy". First post Sep 23, 2026, latest Oct 6, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other GitHub problems
Trouble with GitHub terminalTrouble with GitHub nextGitHub dependency conflicts break installsTrouble with GitHub checkGitHub outages and slowdowns disrupt workMigrating to or off GitHub is slow and riskyGitHub rate limits and usage caps block workRAG on GitHub returns irrelevant or missing contextTrouble with GitHub testGitHub lock-in makes switching costlyGitHub vulnerabilities are hard to triage and patchGitHub deprecations force unplanned migrations
History
rising to fading
Trouble with GitHub proxy (8 posts)