Skip to content

[FR] Make it more obvious when ctags indexing fails #1361

Description

@dsabsay

While setting up a dev environment, I misconfigured the CTAGS_COMMAND which resulted in zoekt being unable to index repositories. Unfortunately, the UI indicated that the indexing was completed successfully. When searching with e.g. sym:main (or any other symbol), 0 results were returned.

This is the error in the logs:

[worker] 2026-06-22T04:37:49.344Z debug: [zoekt] /Library/Developer/CommandLineTools/usr/bin/ctags: illegal option -- -
[worker] 2026-06-22T04:37:49.345Z debug: [zoekt] usage: ctags [-BFTaduwvx] [-f tagsfile] file ...
[worker] 2026-06-22T04:37:49.345Z debug: [zoekt] 2026/06/21 21:37:49 ignoring universal:ctags or scip: error: write |1: file already closed
[worker] 2026-06-22T04:37:49.345Z debug: [zoekt] 2026/06/21 21:37:49 symbol analysis finished for shard statistics: duration=0s symbols=0 bytes=146

I could imagine other scenarios in which ctags indexing might fail. Perhaps the entire index pass should be considered failed in that case? Or at least partially degraded? It's currently impossible to tell from the UI that anything with the indexing is broken.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions