anomalyco / anomalyco/opencode

FFF panics when searching for files

Open
#47,126 0 comments 0 reactions 1 assignee View on GitHub

@simonklee is already working on this.

Since Sep 3, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

By pressing @ in the latest version of opencode fff panics in one of the projects.

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                                                                                                            

This was fixed in FFF, and FFF dependency needs to be updated.

Please see https://github.com/dmtrKovalenko/fff/issues/846

opencode --v
1.18.27
Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.