Issues workflow fails on every opened issue because issues.cjs is called without its arguments
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- github-actions, node.js, typescript
Direzione di ricerca
Read .github/workflows/issues.yaml and .github/scripts/issues.cjs, then compare the script’s assumptions with .agents/skills/opening-issues/SKILL.md and the current issue templates. Verify the workflow behavior by opening and reopening a test issue; done means no failed Issues run and no unwanted title change, or that the obsolete workflow and script are removed.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The "Issues" workflow fails on every issue that is opened or reopened. The workflow calls require('./.github/scripts/issues.cjs')() with no arguments. The module's default export forwards its args parameter to addPriorityAndDifficulty({ context, github }), so the destructure throws TypeError: Cannot destructure property 'context' of 'undefined' before any API call. All 195 runs GitHub still retains failed, from 2025-09-16 to today. The call has had no arguments since the script was moved out of the workflow in Feb 2024. Every new issue therefore adds a red run to the Actions tab and sends a failure notification. A plain fix would also do the wrong thing. The issue templates no longer contain the Priority and Estimated Difficulty sections the script parses, so it would call addLabels with an empty list. .agents/skills/opening-issues/SKILL.md says titles carry no [Bug]:-style prefix, yet the script would add one to every title, and on reopened it would add a second ([Bug]: [Bug]: …).
Where
.github/workflows/issues.yaml:16-20:
- name: Run Script
uses: actions/github-script@v9
with:
script: |
require('./.github/scripts/issues.cjs')()
.github/scripts/issues.cjs:4 and :51-54:
function addPriorityAndDifficulty({ context, github }) {
// ...
module.exports = (args) => {
addPriorityAndDifficulty(args);
addLabelToTitle(args);
};
Reproduce
- Open any issue on the repository.
- Open the triggered "Issues" run (
gh run list --workflow=Issues --limit 1) and read its log.
Actual: ##[error]Unhandled error: TypeError: Cannot destructure property 'context' of 'undefined' as it is undefined. (for example, run 37676175978).
Expected: either the workflow does something useful and succeeds, or it does not exist.
Tests
No unit or Playwright test can run a GitHub workflow. Verify the fix by opening and then reopening a test issue, and confirming that no "Issues" run fails and that the title is unchanged.
Suggested fix
Delete .github/workflows/issues.yaml and .github/scripts/issues.cjs. The templates no longer feed the label step, and the title step contradicts the documented title convention. If automatic labelling is still wanted, reimplement it against the current templates. Pass { context, github } from the workflow, await both API calls, and skip addLabels when there is nothing to add.
- Lingua principale
- TypeScript
- Stelle
- 119
- Fork
- 19
- Merge medio
- 18h 50m
- PR unite (30g)
- 36
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di DouglasNeuroInformatics/OpenDataCapture
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
DouglasNeuroInformatics/OpenDataCapture#1813 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
DouglasNeuroInformatics/OpenDataCapture#1812 ·
I maintainer di solito rispondono entro 1 giorno
-
Area: Playground Bug Difficulty: Low Good First Issue Priority: Low
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
DouglasNeuroInformatics/OpenDataCapture#1805 ·
I maintainer di solito rispondono entro 1 giorno
-
Area: Instruments Bug Difficulty: Low Priority: Low
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
DouglasNeuroInformatics/OpenDataCapture#1801 ·
I maintainer di solito rispondono entro 1 giorno
-
Area: Instruments Bug Difficulty: Low Good First Issue Priority: Low
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
DouglasNeuroInformatics/OpenDataCapture#1800 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di DouglasNeuroInformatics/OpenDataCapture
Issue simili
-
bug require-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
expressjs/expressjs.com#2549 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
umami-software/umami#4686 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --displayForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
pingdotgg/t3code#24900 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
inu-appcenter/UNIDorm-web#411 ·
I maintainer di solito rispondono entro 1 giorno
-
🐛 bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 2 giorni