[GLOW] feedback: fix #90

Activity

1. accesswatch

   added

   needs-triageNew issue awaiting first maintainer responseNew issue awaiting first maintainer response

   on Aug 21, 2026
2. github-actions commented on Aug 21, 2026

   

   github-actionsbot

   on Aug 21, 2026 – with GitHub Actions

   More actions

   Thanks for opening this request. A maintainer will review it within 24 to 48 hours.
3. accesswatch commented on Aug 21, 2026

   

   accesswatch

   on Aug 21, 2026

   ContributorAuthor

   More actions

   Triaged: this is not user feedback. It was filed by GLOW's own test suite.

   tests/test_app.py::TestFeedback posts feedback through the real route
   without stubbing the support-hub sender, so on any machine whose environment
   carries FEEDBACK_GITHUB_TOKEN — a developer shell, a deploy shell — running
   the web suite opened two live issues here, one for audit and one for fix.
   The Feedback ID: 1 on every one of these is the giveaway: a fresh temporary
   database per run.

   Fixed in Community-Access/glow@2080537:

   • An autouse fixture clears every SUPPORT_HUB_* and FEEDBACK_* variable
     for every test, so a test run can no longer reach this tracker at all.
   • Only categories that need a person — bug, accessibility, regression,
     support — open an issue. Praise and general comments are still stored and
     still shown in the admin feedback list. SUPPORT_HUB_ISSUE_CATEGORIES=all
     restores the old behaviour.
   • Identical submissions within 24 hours open one issue rather than several.

   Closing as automation noise. No user is waiting on a reply here.
4. accesswatch

   closed this as not plannedon Aug 21, 2026