2026.10.9 (#172) creates an (account, column) index for every sorted search column. The tracing table s_trace has no account column, so on every start each node logs:
WARN Configuration build warning (registry.build-warning) source = SearchStore ... Failed to create search indexes: ... column "accid" does not exist
The search store is still built and used (storage.rs only warns), and the indexes on s_email, s_cal and s_card were created. The composite index is now only made where the table's primary key includes the account. For the next release.
2026.10.9 (#172) creates an (account, column) index for every sorted search column. The tracing table s_trace has no account column, so on every start each node logs:
WARN Configuration build warning (registry.build-warning) source = SearchStore ... Failed to create search indexes: ... column "accid" does not exist
The search store is still built and used (storage.rs only warns), and the indexes on s_email, s_cal and s_card were created. The composite index is now only made where the table's primary key includes the account. For the next release.
2026.10.9 added an (account, column) index for every sorted search
column, but the tracing table has no account column, so each node
logged a build warning at startup for the one CREATE INDEX that failed.
The index is now only made where the table's primary key has the
account.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
2026.10.9 (#172) creates an (account, column) index for every sorted search column. The tracing table s_trace has no account column, so on every start each node logs:
The search store is still built and used (storage.rs only warns), and the indexes on s_email, s_cal and s_card were created. The composite index is now only made where the table's primary key includes the account. For the next release.