Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Tracking: open issues by priority (2026-09-28 convergence pass)

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
java, kotlin
Ambito
documentation, tooling

Direzione di ricerca

This is a tracking index of many open issues, not a single change. Do not implement from this ticket. Pick one named child issue (for example CodeLaser/maddi#4 javadoc CI noise, or a Tier 1 row) and work from that issue’s first-step column. Done here would only mean the table is kept in sync after those issues close.

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

Descrizione

Every open issue as of 2026-09-28, after the convergence pass that closed 30 of 59 (fixed on devel or on ws/dsl that day) and fixed CodeLaser/maddi#22, CodeLaser/maddi#30, CodeLaser/maddi#31, CodeLaser/maddi#40, CodeLaser/maddi#60, CodeLaser/maddi#64 (items 2, 3), CodeLaser/maddi#66 directly. Ordered by cost/benefit within each tier; sizes are S (hours), M (a day or two), L (design first). "Owner" is the branch that has been working the area.

Tier 1: small, unblocks something, do next

# issue size why now first step
CodeLaser/maddi#68 Kotlin body call to a Java-source member does not resolve S-M blocks the downstream unmodifiable-collection diagnostic add the J.fill / J().put shape to TestMixedProjectInspector, assert no k2-unresolved-call; fix likely in members() for a Java-source TypeInfo whose members are not loaded when Kotlin bodies convert (ws/python)
CodeLaser/maddi#67 printed Kotlin does not compile: smart-cast comparison S one fixture tells whether the last placeholder in that list is already gone since 69c94b14f add when (o) { is Int -> if (o > 10) ... } to WhenSeveralIsTest; raise the jar-name mismatch log to WARN; close items 3 and 4 as intended
CodeLaser/maddi#64 (item 1) Collections.sort's list not @Modified in the JSON M every Collections/Arrays mutator reads undecided codec writes unmodifiedParameter:0 (or the loader reads absence on an annotated-API parameter as decided false), then annotate sort, reverse, shuffle, ...
CodeLaser/maddi-mod#7 hints compiler computes libs/test, libs/log defaults without the jdk results S code, M validation wrong defaults for String/CharSequence parameters in two libraries pass the jdk preload to the shared compiler in CompileAnalysisHints, regenerate, corpus A/B as the issue asks
CodeLaser/maddi#15 LinksImpl.equals ignores linkSet S last-wins exists (f747b2105, WIP under the merge) but nothing pins it fast test for last-wins in VariableInfoImpl.setLinkedVariables; decide whether the primary-change throw is reachable; squash the WIP
CodeLaser/maddi#4 javadoc warnings on CI S the only noise on a clean CI run javadoc on Commutable's members, or one Xdoclint block in the convention plugin
CodeLaser/maddi-dist#1 IDE: coalesced triggers dropped S a silently lost build is user-visible PENDING flag beside RUNNING in MaddiAnalysis (Eclipse) and MaddiAnalysisService (IntelliJ), reschedule once in finally

Tier 2: medium, scheduled work

# issue size note
CodeLaser/maddi#5 no Gradle toolchain; dev on 27, CI on 26 M now real drift; needs a build to validate, do with the next JDK-27 CI bump
CodeLaser/maddi#69 lowered <i>.0/.1 indices lose the local at <i+1> M per-block renumbering after building; touches every lowering test's indices (ws/python)
CodeLaser/maddi#19 VariableData order non-deterministic S-M sort by source position at build(); risk to this/fields/params-first consumers
CodeLaser/maddi-mod#3 no version/schema marker in analysis results S-M header field + check in LoadAnalysisResults
CodeLaser/maddi-mod#10 fork for switch, loop, try; exclude exiting branches M per step six-corpus A/B each; NOFORK gate stays
CodeLaser/maddi-mod#5 full-pipeline crash survey M build on RunAnalyzer fault-tolerant listing + the corpus catalogue; bucket by (exception, class:line)
CodeLaser/maddi#58 non-local return: owner decision decision marker (current) vs refuse vs inline scope functions for the 125 detekt sites under analyze{}; then close as "front end done, engine in CodeLaser/maddi-mod#11"
CodeLaser/maddi-dist#2 Eclipse: whole-workspace marker churn S-M per-file delete; prerequisite of CodeLaser/maddi-dist#3
CodeLaser/maddi-mod#12 Elasticsearch variablesLinkedToObject@LCI oscillation M re-run on devel with the per-iteration change log; latest-wins may have changed it
CodeLaser/maddi#49 printer: brace placement, literal spelling, comment fidelity L, split in 3 (a) bracePlacement option, (b) carry literal source text from javac, (c) comment/blank-line fidelity

Tier 3: design first

# issue note
CodeLaser/maddi-mod#11 link engine ignores exitLevels (non-local return value never reaches the enclosing return) soundness hole; start with the S fixture asserting find's return variable links to xs
CodeLaser/maddi-mod#9 reassigned parameter's later values summarised as facts about the caller's object SSA-style rename from the first reassignment
CodeLaser/maddi-mod#8 method summaries mark a parameter modified, never which part field-path modification in summaries
CodeLaser/maddi-mod#6 Cassandra does not converge re-run on devel with the change log after latest-wins; profiling + partial reporting
CodeLaser/maddi-dist#3 Eclipse builder / project nature days; depends on the daemon accepting a scope
CodeLaser/maddi-dist#4 Eclipse quick fixes needs an edit protocol from the daemon
CodeLaser/maddi-dist#5 Eclipse GUI install path 30 min manual, whoever next has Eclipse open
CodeLaser/maddi-mod#1, CodeLaser/maddi-mod#2 tracking issues progress comments posted 09-28; keep as indexes
Lingua principale
Java
Stelle
1
Fork
1
Merge medio
2h 51m
PR unite (30g)
3

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 CodeLaser/maddi

Tutte le issue di CodeLaser/maddi

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.