feat(memory): implement conversation_analyze job handler#25666
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 941be91fd0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Already addressed in #25676 (different approach): the handler now returns early when getAnalysisDeps is null, letting upstream triggers re-enqueue naturally instead of deferring. See the in-file comment in conversation-analyze-job.ts for the rationale (defer counters would still fail permanently in worst case; early return avoids retry storms during slow startup). |
Summary
conversationAnalyzeJobhandler that retrieves deps via the singleton and callsanalyzeConversation(id, deps, { trigger: "auto" }).jobs-worker.tsnext tograph_extract.Part of plan: auto-analyze-loop.md (PR 13 of 15)