Skip to main content
← Back to list
01Issue
BugClosedSwamp Club
AssigneesNone

Relationships

#1023 Beta-channel extensions are never scored — perpetual 'Scoring is taking longer than expected'

Opened by magistr · 7/7/2026

Correction (rewritten): the first version of this report claimed a platform-wide scoring outage since ~2026-07-04 across all channels. That was wrong — it was an artifact of my method (swamp extension search --json omits the score field entirely, so every row read as "unscored" when the field was simply never projected; see #1024). Per-extension swamp extension info shows stable extensions are scored. The real, narrower issue is below: beta-channel extensions are not scored.

Summary

Extensions released to the beta channel never receive a quality score. Their detail pages on swamp.club show, indefinitely:

ERR: Scoring is taking longer than expected. Refresh the page in a moment to check the result.

Refreshing never resolves it. On the beta-channel view essentially every extension is unscored (one exception observed). Stable-channel extensions score normally.

Environment

  • CLI version: 20260707.202458.0-sha.17103ab8
  • Account: magistr
  • Observed: 2026-07-07 / 2026-07-08

Reproduction

  1. Publish an extension to beta only: swamp extension push <manifest> --channel beta.
  2. Open its detail page on swamp.club → "Scoring is taking longer than expected…" that never resolves.
  3. From the CLI: swamp extension info <name> --jsonlatestVersion: null, latestBeta: <ver>, "score": null.

Evidence

Beta-only extension — unscored:

$ swamp extension info @magistr/stripe-mpp --json
  "latestVersion": null,
  "latestBeta": "2026.07.03.1",
  "score": null

Stable extensions checked individually via swamp extension infoall scored (each has latestVersion set, latestBeta: null, and a populated score): @swamp/gcp/compute, @figura/cribl-stream, @jamesakeech/spotify, @keeb/peloton-rides, @dougschaefer/azure, @atalanta/meta-factory — plus older ones like @goodcraft/stripe, @magistr/career-kb, @magistr/pihole.

The web UI's beta-channel view additionally shows ~every beta extension unscored with the same timeout message (only one scored exception observed) — consistent with the scorer not running (or not persisting a score) for beta/pre-release versions.

Impact

  • Extensions in beta/pre-release get no score, so publishers testing via the beta channel can't see rubric results before promoting to stable.
  • The beta-channel browse view is effectively all-unscored, and the "refresh in a moment" hint is misleading — it reads as transient when the score never arrives.

Likely area

The extension rubric scorer appears to only run/persist for stable (and rc?) releases, not beta — or the beta scoring path stalls and the job never completes (matching the perpetual "taking longer than expected" state). Worth checking whether the scorer is enqueued at all on a --channel beta push.

  • #1024swamp extension search --channel filter is ignored (all channels return the same set), which is why beta extensions can't be enumerated from the CLI to audit this. (Not the cause of the scoring gap, but it blocked the investigation.)
02Bog Flow
OPENTRIAGEDIN PROGRESSCLOSED

Closed

7/7/2026, 11:21:44 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 7/7/2026, 11:21:43 PM

Closing as a dupe of #1025

Sign in to post a ripple.