Set SUPABASE_SERVICE_ROLE_KEY worker secret (paper-request form errors until then)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- supabase, typescript
Research direction
Start with src/lib/paper-requests.functions.ts and CUTOVER.md § Phase 0, then check the worker secret list and the Supabase project configuration. The work is complete when the deployed /benchmarks form submits successfully and a row appears in the paper_requests table.
Written by the indexing model from the issue text.
Description
The paper-request form on /benchmarks fails on submit because the worker secret SUPABASE_SERVICE_ROLE_KEY is not set (wrangler secret list returns []). Everything else on the site works.
The form's server function (src/lib/paper-requests.functions.ts) writes to the paper_requests table in the Supabase project ulrbnkrvxzbtqancxmtn (created by Lovable) and reads the key from process.env.
Steps
- Get the key: supabase.com/dashboard → project
ulrbnkrvxzbtqancxmtn→ Project Settings → API Keys → reveal the service_role secret (startssb_secret_). If the project isn't listed under your account, reach it through the hello-bright project's Cloud panel in Lovable. This is NOT thesb_publishable_key already committed in.env. npx wrangler loginas kevin@app.land if needed, then:
npx wrangler secret put SUPABASE_SERVICE_ROLE_KEY- Redeploy (push any commit, or
npm run build && npx wrangler deploy) — secrets take effect on the next deploy. - Verify: submit the form on https://appmap.io/benchmarks and expect a success message; confirm a row lands in
paper_requests.
See CUTOVER.md § Phase 0 for the full context.
🤖 Generated with Claude Code
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getappmap/appmap.io
All issues in getappmap/appmap.io
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100