Formal models and scripts: hunspell-set-encoding-names-vs-c-hunspell-reference

Tools: Python

These are the working models and scripts this part of the hunt used. Some encode the code as it is (a counterexample is the expected result), others a fixed or correct variant; read the header comment of each file. Paths inside them were replaced by placeholders such as $LUCENE (a Lucene checkout) and $WORK.

Findings

• Hunspell Dictionary can fail to load with 'Too many collisions' when its entry count is a multiple of 961, because WordStorage takes the raw String.hashCode() modulo the table size (for example the en_US dictionary plus a 300-word custom list) (finding LFV-933; repro · finding page)
• Hunspell Dictionary cannot load SET ISO8859-10, or ISO8859-14 spelled any way except exactly "ISO8859-14" (UnsupportedCharsetException at load) (finding LFV-928; repro · finding page)

Files

• hunspell-set-encoding-name-table-incomplete/model/expected_all_bytes.py (used for LFV-928)
• hunspell-wordstorage-hash-modulo-multiple-of-31/model/slot_counts.py (used for LFV-933)

How to run

• Python: python3 <file>.py; scripts that import z3 need the z3-solver package.

Snapshot of 2026-11-03. AI-assisted; not yet triaged by a human Lucene committer. Feedback: open an issue in lucene-ai-bug-hunt.