Triage: #42 "Export to CSV crashes"
Recommendation: category bug, state needs-info. The issue is unlabeled now. The normal path is needs-triage first, but I think it can go straight to needs-info. Either way, the label change and comment wait for your go-ahead.
What I checked
- Prior rejection: there is no
.out-of-scope/directory, so there is no earlier rejection to surface. - Redundancy: this is a crash report, not a feature request, so an existing implementation doesn't apply.
- Codebase: I couldn't explore it. The working directory isn't a git repo, and I only have a file reader here, with no way to list directories or search. I didn't want to guess at paths. If you tell me where the reports page and its export handler live, I'll trace the code path.
- Reproduction: not attempted. There's no running app or repro data, and the report has no steps I could follow.
Why needs-info
The report is too thin to reproduce or to write a durable agent brief from:
- "Spins forever, then the page goes blank" could be a hung request or a server timeout. It could also be an unhandled client-side exception or a memory blowup on a large dataset.
- "Happens on my laptop" gives no browser, OS or app version.
- It doesn't say whether the export works for smaller reports, other reports or other users.
Draft comment (not posted)
> *This was generated by AI during triage.*
## Triage Notes
**What we've established so far:**
- Clicking Export on the reports page shows a spinner that never finishes, then the page goes blank.
- Reported on the reporter's laptop only; we haven't seen it elsewhere yet.
**What we still need from you (@sam):**
- Which report were you exporting, and roughly how many rows does it have? Does a smaller report or a narrower date range export fine?
- Which browser and version are you using, and which OS?
- Open the browser dev tools (Console and Network tabs) and click Export again. Is there a red error in the Console? Does the export request show a status code, or stay "pending"? Please paste what you see.
- Does it fail every time, or only sometimes? Does it also fail for a teammate or on another machine?
- Which app version or deploy are you on?
Next step: should I apply bug + needs-info and post that comment? Or would you rather go to needs-triage first, or give me the code location so I can try to verify the crash from the source before asking @sam anything?
How it was tried: I installed triage together with the grilling and domain-modeling skills it can call, in a clean temporary folder, and invoked it as a slash command with one pasted issue and no issue tracker connected. Only Skill and Read tools were allowed, so nothing was posted, labelled or closed, the codebase could not be explored and no bug was reproduced. It shows only the recommend step and a drafted comment, and it stops to wait for your go-ahead.
Qué hace
Un flujo para mantenedores. Cada incidencia —y cada solicitud de cambios externa, tratada como una incidencia con código adjunto— pasa por dos roles de categoría (bug, enhancement) y cinco roles de estado (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).
Cómo funciona
- Muestra lo que necesita atención: elementos sin etiqueta, con
needs-triagey conneeds-infoque tienen respuestas nuevas. - Para cada elemento, lo lee completo, comprueba si el comportamiento ya está implementado y consulta las notas de
.out-of-scope/por si se rechazó antes. - Recomienda una categoría y un estado, y espera tus indicaciones.
- Verifica lo afirmado: reproduce el error o confirma que una PR hace lo que dice.
- Si hace falta precisar la propuesta, inicia una sesión de
grilling+domain-modeling. - Aplica el resultado: instrucciones para un agente, notas de clasificación o un cierre con explicación. Las guías incluidas explican cómo redactar instrucciones duraderas para agentes y mantener la base de conocimiento
.out-of-scope/.
Para qué sirve
Mantenedores de proyectos con muchas incidencias. Publica comentarios y puede cerrar incidencias: revisa cada acción.
Riesgo alto: actúa en tu gestor de incidencias, aplica etiquetas, publica comentarios (con aviso inicial de generación por IA) y puede cerrar incidencias. Para errores o PR externas puede reproducir el fallo o descargar la PR y ejecutar sus pruebas: usa código sin revisar; emplea un entorno aislado o un clon limpio para PR no confiables. También escribe archivos (`.out-of-scope/`, glosario o ADR). Primero debe recomendar y esperar tus indicaciones; revisa cada acción antes de aprobarla. Necesita tu correspondencia de etiquetas y las Skills `grilling` y `domain-modeling`. Se probó con una incidencia pegada, sin gestor conectado ni herramientas de archivos o shell: solo se observaron la recomendación y un comentario en borrador. No publicó, etiquetó ni cerró nada, no reprodujo errores ni descargó PR.