Repository navigation
[AI-186] States and background processing for Semantic Indexes - #7
Open
xhr15 wants to merge 7 commits into
Conversation
|
Caution The provided work package version does not match the core version Details:
Please make sure that:
|
xhr15
force-pushed
the
implementation/ai-186-states-and-background-processing-for-semantic-indexes
branch
from
October 16, 2026 11:03
3e306fe to
dc2ec18
Compare
joelpaulkoch
force-pushed
the
implementation/ai-178-crud-for-semantic-indexes
branch
from
October 16, 2026 12:30
bc3cca3 to
b960cfe
Compare
Semantic Indexes move from not_indexed through indexing to ready or failed. A placeholder job decides the outcome at random until the real indexing is wired in. https://community.openproject.org/wp/AI-186
Model, context length and dimensions stay editable only while a Semantic Index has not been indexed. Name and description remain editable in every state.
Only a ready Semantic Index can be activated, and the active one cannot be deleted. Embedding and search still read the binding's model.
The active Semantic Index is pinned above the others in the semantic search box, with an empty state while none is active. Ready indexes can be activated after a confirmation.
joelpaulkoch
force-pushed
the
implementation/ai-186-states-and-background-processing-for-semantic-indexes
branch
from
October 16, 2026 13:20
dc2ec18 to
1c9d43b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/wp/AI-186
What it's about:
Semantic Indexes get states and (simulated) background indexing. Admins can activate a ready Semantic Index for semantic search.
not_indexed→indexing→ready/failed. Admins can start indexing from the row menu: "Start indexing", "Retry indexing" after a failure, or "Re-index" when ready. The list refreshes once indexing ends, without a reload.The indexing job is simulated. Real embedding comes in a follow-up.
Screenshots
What approach did you choose and why?
State machine: a string-backed enum with explicit transition methods (
start_indexing!,finish_indexing!,fail_indexing!). Each transition runs under a row lock and raises on an invalid transition. Statesman might be another alternative from the codebase, but this approach was more commonBackground processing:
Llm::BuildSemanticIndexJob(GoodJob) stands in for the real indexing and randomly succeeds or fails. this is a placeholder for the logic already on the target branch A!-163Activation:
LlmFeatureBindinghas asemantic_indexreference, so there is exactly one active index per feature.ActivateServiceswitches it, and contracts guard the ready-only and no-delete-while-active rules.Locking: the update contract rejects parameter changes once the index has left
not_indexed, and the form disables those fields and shows a banner.The commits are meant to be reviewed one by one.
AI involvement
None/Assisted – No AI assistance used OR only autocomplete/pasted snippets. I effectively wrote and understand all the code.