Summarize existing IDE runtime errors without launching or rebuilding the IDE

Aperta
  • Qualcosa non va?
#47 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
node.js
Ambito
build-system

Direzione di ricerca

Start by reading build/check.mjs, build/check-build.mjs and build/run.mjs to see how existing modes (like --compile) are dispatched and reported, then design a new log-audit mode that takes a path to an existing idea.log without launching the IDE. Group errors per startup session, dedupe repeated exception signatures with first/last locations, and separate warnings, severe errors and expected shutdown cancellation. Done means tiny fixtures for multiple sessions, truncated stack traces and repeated bundle errors exercise both the bounded JSON output and the sanitized text report.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted priority medium tooling

Problem / current evidence

check.mjs --compile summarizes compilation only. Actual missing-bundle and service-registration problems were found manually in idea.log, and the log contains multiple startup sessions and expected shutdown noise.

Code references

Scope / proposed contract

Add an explicit log-audit mode that reads a user-selected existing idea.log, selects a startup session and groups actionable errors with timestamps/counts. Keep the original log untouched and do not start the IDE.

Completion criteria

  • Separate sessions and label old logs with their recorded product/build/time instead of claiming current-source reproduction.
  • Group repeated exception signatures while retaining first/last locations and representative context.
  • Distinguish warnings from severe errors and do not blanket-classify expected shutdown cancellation as startup failure.
  • Offer bounded JSON output and a portable sanitized text report; do not upload logs automatically.
  • Use tiny fixtures for multiple sessions, truncated stack traces and repeated bundle errors.

Dependencies and boundaries

  • No implementation dependency in this backlog; keep this PR focused on the scope above.
  • Backlog index: #8.
  • Validation listed above is acceptance work, not a claim that it has already passed. Prefer targeted fixtures; run full compilation or an IDE session only when the task requires it.

Difficulty

Medium — requires familiarity with the affected integration or build tooling.

Audit baseline: 2804fc02. No code changes are included in this issue.

Lingua principale
Java
Stelle
0
Fork
3
Merge medio
8h 8m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/wave-for-platform

Tutte le issue di wavefnd/wave-for-platform

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.