CI fixes#290
Merged
Merged
Conversation
Collaborator
luarss
commented
Jun 5, 2026
luarss
commented
- async retriever graph - so its no longer a blocker for docker healthcheck
- reduce docker healthcheck timeout
- add for loop for health check simulation block in secret ci
Split document embedding into 100-chunk batches with a 1s delay between batches so a 429 only retries one batch (~1 API call) rather than restarting FAISS.from_documents from scratch (~87 calls). Also raise retry wait times from max 120s to max 600s to give the quota time to reset before the next attempt. Signed-off-by: Jack Luar <jluar@precisioninno.com>
Move RetrieverGraph construction out of module-level import in conversations.py and into a background thread spawned during the FastAPI lifespan. This lets the server start instantly so the Docker health-check passes within the reduced 30 s start_period (instead of timing out after 22+ min waiting for FAISS embedding). - Replace module-level rg = RetrieverGraph(...) with lazy singleton (get_graph / start_graph_init / reset_graph_state_for_testing) - Add /conversations/ready readiness probe returning 'ready' or 'initializing' - Conversation endpoints return 503 / stream error when graph is not yet initialized - Add readiness poll loop (30 min, 10 s intervals) before Run LLM CI step in ci-secret.yaml - Reduce Docker healthcheck start_period default from 1200 s to 30 s - Update streaming tests to use new public reset_graph_state_for_testing() Signed-off-by: Jack Luar <jluar@precisioninno.com>
luarss
added a commit
to luarss/ORAssistant
that referenced
this pull request
Jun 6, 2026
* fix: defer graph init to background, prevent health-check timeout Move RetrieverGraph construction out of module-level import in conversations.py and into a background thread spawned during the FastAPI lifespan. This lets the server start instantly so the Docker health-check passes within the reduced 30 s start_period (instead of timing out after 22+ min waiting for FAISS embedding). - Replace module-level rg = RetrieverGraph(...) with lazy singleton (get_graph / start_graph_init / reset_graph_state_for_testing) - Add /conversations/ready readiness probe returning 'ready' or 'initializing' - Conversation endpoints return 503 / stream error when graph is not yet initialized - Add readiness poll loop (30 min, 10 s intervals) before Run LLM CI step in ci-secret.yaml - Reduce Docker healthcheck start_period default from 1200 s to 30 s - Update streaming tests to use new public reset_graph_state_for_testing() Signed-off-by: Jack Luar <jluar@precisioninno.com> --------- Signed-off-by: Jack Luar <jluar@precisioninno.com>
luarss
added a commit
to luarss/ORAssistant
that referenced
this pull request
Jun 6, 2026
* fix: defer graph init to background, prevent health-check timeout Move RetrieverGraph construction out of module-level import in conversations.py and into a background thread spawned during the FastAPI lifespan. This lets the server start instantly so the Docker health-check passes within the reduced 30 s start_period (instead of timing out after 22+ min waiting for FAISS embedding). - Replace module-level rg = RetrieverGraph(...) with lazy singleton (get_graph / start_graph_init / reset_graph_state_for_testing) - Add /conversations/ready readiness probe returning 'ready' or 'initializing' - Conversation endpoints return 503 / stream error when graph is not yet initialized - Add readiness poll loop (30 min, 10 s intervals) before Run LLM CI step in ci-secret.yaml - Reduce Docker healthcheck start_period default from 1200 s to 30 s - Update streaming tests to use new public reset_graph_state_for_testing() Signed-off-by: Jack Luar <jluar@precisioninno.com> --------- Signed-off-by: Jack Luar <jluar@precisioninno.com> Signed-off-by: Jack Luar <jluar@precisioninno.com>
luarss
added a commit
to luarss/ORAssistant
that referenced
this pull request
Jun 6, 2026
* fix: defer graph init to background, prevent health-check timeout Move RetrieverGraph construction out of module-level import in conversations.py and into a background thread spawned during the FastAPI lifespan. This lets the server start instantly so the Docker health-check passes within the reduced 30 s start_period (instead of timing out after 22+ min waiting for FAISS embedding). - Replace module-level rg = RetrieverGraph(...) with lazy singleton (get_graph / start_graph_init / reset_graph_state_for_testing) - Add /conversations/ready readiness probe returning 'ready' or 'initializing' - Conversation endpoints return 503 / stream error when graph is not yet initialized - Add readiness poll loop (30 min, 10 s intervals) before Run LLM CI step in ci-secret.yaml - Reduce Docker healthcheck start_period default from 1200 s to 30 s - Update streaming tests to use new public reset_graph_state_for_testing() Signed-off-by: Jack Luar <jluar@precisioninno.com> --------- Signed-off-by: Jack Luar <jluar@precisioninno.com> Signed-off-by: Jack Luar <jluar@precisioninno.com>
luarss
added a commit
to luarss/ORAssistant
that referenced
this pull request
Jun 6, 2026
* fix: defer graph init to background, prevent health-check timeout Move RetrieverGraph construction out of module-level import in conversations.py and into a background thread spawned during the FastAPI lifespan. This lets the server start instantly so the Docker health-check passes within the reduced 30 s start_period (instead of timing out after 22+ min waiting for FAISS embedding). - Replace module-level rg = RetrieverGraph(...) with lazy singleton (get_graph / start_graph_init / reset_graph_state_for_testing) - Add /conversations/ready readiness probe returning 'ready' or 'initializing' - Conversation endpoints return 503 / stream error when graph is not yet initialized - Add readiness poll loop (30 min, 10 s intervals) before Run LLM CI step in ci-secret.yaml - Reduce Docker healthcheck start_period default from 1200 s to 30 s - Update streaming tests to use new public reset_graph_state_for_testing() Signed-off-by: Jack Luar <jluar@precisioninno.com> --------- Signed-off-by: Jack Luar <jluar@precisioninno.com>
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
1 participant
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.