aethersdr / aethersdr/AetherSDR

CI: Mirror Aether-gate fails on every run — MIRROR_SYNC_TOKEN lacks the `workflow` scope (mirror 86 commits behind)

Open
#5,302 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug maintainer-review
Dominant language
C++
Stars
221
Forks
117
Avg merge
2d 7h
Merged PRs (30d)
299

Description

Mirror Aether-gate has been failing on every scheduled run since well before the
visible run history begins, so aethersdr/Aether-gate has drifted a long way behind
its upstream. Raising it because the job is deliberately quiet — it only surfaces in
the Actions tab, and it no-ops rather than failing when unconfigured, so a real failure
looks much like the intended silence.

The error

From the most recent run (33133278635):

Upstream commits contain workflow changes, which require the `workflow` scope
or permission to merge. To request it, run: gh auth refresh -s workflow

MIRROR_SYNC_TOKEN is authorised for contents but not workflows. GitHub refuses a
sync outright when any pending commit touches .github/workflows/, so this is not
limited to the commits that caused it — every subsequent commit is blocked too.

Two commits upstream trip it, both mine, around 15–16 July: one added
.github/workflows/docker.yml, one modified .github/workflows/tests.yml.

Current state

Scheduled runs 300 visible, 0 successes
Oldest visible run 2026-08-19 (already failing; first blocking commit is ~a month earlier)
Mirror behind by 86 commits
Mirror main fb46af84, dated 2026-07-15
Upstream main b8ad65ba, dated 2026-08-24

Fix

Add the workflow scope to the PAT behind MIRROR_SYNC_TOKEN. The backlog should
fast-forward on the next scheduled run; no change to
.github/workflows/mirror-aether-gate.yml
is needed.

Why it may be worth doing rather than leaving

The mirror predates the HPSDR Protocol-1 adapter, the RX audio path, the IQ
conjugation fix (inverted sideband) and the IC-9700 CI-V SET-menu work.

It also predates 57d6c67c, which retracts an earlier stream-starvation claim as a
measurement error — so the org's copy currently carries the claim without the
retraction. Anyone reading aethersdr/Aether-gate today is reading July, including
one conclusion that has since been withdrawn.

No objection at all if the answer is to retire the mirror instead of maintaining a
token for it — nigelfenton/Aether-gate
is public and current either way. Flagging it rather than assuming which way you'd want
it to go.


Filed outside the issue templates deliberately: bug_report.yml requires radio model,
OS and AetherSDR version, none of which apply to a CI credential scope.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with .github/workflows/mirror-aether-gate.yml and failed run 33133278635; compare the token permissions with the reported workflow-scope error. Confirm the chosen outcome—restore the mirror or retire it—and, if maintained, verify a scheduled run synchronizes the 86-commit backlog.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.