fff scan regression in 1.17.1 breaks startup on NFS mounts #31850

Activity

1. github-actions

   assigned

   StarpTech

   on Jun 11, 2026
2. github-actions commented on Jun 11, 2026

   

   github-actionsBot

   on Jun 11, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Steps to reproduce is empty (_No response_) — please describe how to trigger the issue
   • Operating System is empty — please include your OS details
   • Description mismatch — the title says "NFS mounts" but the description only mentions "large number of files" with no mention of NFS; please make sure the description matches the actual problem you are reporting

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • v1.17.x regression: 'fff scan timed out' crashes app in home directory #31682: v1.17.x regression — 'fff scan timed out' crashes app in home directory (same fff scan regression in 1.17.x, now closed/fixed)
   • fff scan timed out when starting opencode from home directory containing OneDrive File Provider trees 1.17.0+ #31747: fff scan timed out when starting opencode from home directory containing OneDrive File Provider trees 1.17.0+ (same fff scan timeout, different filesystem, now closed)
   • 1.17.1 TUI exits with Unexpected server error when started from large home directory #31701: 1.17.1 TUI exits with Unexpected server error when started from large home directory (same version, same symptom, now closed)

   Note: the fff scan timeout issue appears to have been fixed in v1.17.3. If you are still experiencing this on a recent version, please confirm your version and clarify what is different about NFS mounts specifically.

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 11, 2026
4. github-actions commented on Jun 11, 2026

   

   github-actionsBot

   on Jun 11, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

   Feel free to open a new issue that follows our issue templates.
5. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 11, 2026
6. github-actions

   closed this as not plannedon Jun 11, 2026