[Bug]: FFF panics in opencode

[rushter]

Which fff frontend?

Other / multiple

has logs

thread '<unnamed>' (466241) panicked at crates/fff-core/src/simd_path.rs:109:13:                                                                                            
index out of bounds: the len is 32 but the index is 32ild ·                                                                          
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀                                                
                                           thread '<unnamed>' (466187) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/neo_frizbee-0.10.2/src/one_shot/parallel.rs:181:40:               
called `Result::unwrap()` on an `Err` value: Any { .. }                                                                                                                     
fatal runtime error: failed to initiate panic, error 5, aborting                                                                                                            

Description

By pressing in @ in the latest version of opencode I now get panics.

opencode --v
1.18.27

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 25.04
Release:        25.04
Codename:       plucky

lscpu

  Model name:                Intel Core Processor (Haswell, no TSX)
    CPU family:              6
    Model:                   60
    Thread(s) per core:      1
    Core(s) per socket:      1
    Socket(s):               6
    Stepping:                1
    BogoMIPS:                4788.90
    Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good no
                             pl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
                              rdrand hypervisor lahf_lm abm cpuid_fault pti tpr_shadow flexpriority ept vpid ept_ad fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat 
                             vnmi md_clear

[dmtrKovalenko]

@gustav-fff was this fixed?

[gustav-fff]

[triage-bot] POTENTIALLY FIXED: Likely fixed by #655 (8c76a1b, 2026-07-07), first stable release v0.10.0.

resolve_ptrs iterated self.indices.len() over a fixed [*const u8; 32] buffer (32 chunks x 16 bytes = 512 bytes of path). Any path longer than 512 bytes hit buf[32]:

index out of bounds: the len is 32 but the index is 32

The second trace is just the rayon worker re-panicking that same payload.

Confirming evidence you are on a pre-fix build: your log names neo_frizbee-0.10.2. #655 bumped that pin to 0.10.4 as part of the fix, so your binary is older than v0.10.0. Current main pins 0.11.0.

Verified on origin/main (d84c0a1) that the guard and the regression tests are in place:

cargo test -p fff-search --lib 512
test simd_path::tests::test_resolve_ptrs_path_exceeding_512_bytes ... ok
test score::filename_bonus_tests::test_path_longer_than_512_bytes_does_not_panic_and_matches ... ok

@rushter your opencode ships fff bundled, so updating opencode is not enough by itself - it has to bundle fff >= v0.10.0. Check what it resolved and retest, then report back.

Honk-Honk 🪿