LCORE-470: Fix agent initialization in streaming_query

[jrobertboos]

Description

Fixed the bug about requiring the agent to be initialized in streaming_query.

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue LCORE-470
• Closes LCORE-470

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

• Bug Fixes
  • Improved reliability by ensuring agents are fully initialized before use in streaming queries.

[coderabbitai]

Walkthrough

An explicit asynchronous call to agent.initialize() is added immediately after creating the AsyncAgent instance in the streaming query endpoint. This ensures the agent is initialized before any further operations. No other logic or public interfaces are modified.

Changes

Cohort / File(s)	Change Summary
Agent Initialization in Streaming Query src/app/endpoints/streaming_query.py	Added an explicit asynchronous call to agent.initialize() after AsyncAgent instantiation to ensure proper initialization before reuse or assignment.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Endpoint
    participant AsyncAgent

    Client->>Endpoint: Send streaming query request
    Endpoint->>AsyncAgent: Instantiate AsyncAgent
    Endpoint->>AsyncAgent: await initialize()
    Endpoint->>AsyncAgent: Further logic (reuse, assign conversation ID, etc.)
    AsyncAgent-->>Endpoint: Ready for processing
    Endpoint-->>Client: Continue response flow

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5-10 minutes

Poem

A hop and a skip, the agent awakes,
With initialize() called for safety’s sake.
Before it can chat, or answer a plea,
It’s ready and waiting, as quick as can be.
In streaming queries, no bugs to fear—
The rabbit ensures all starts are clear! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3b530d and 0662678.

📒 Files selected for processing (1)

• src/app/endpoints/streaming_query.py (1 hunks)

🔇 Additional comments (1)

src/app/endpoints/streaming_query.py (1)

76-77: LGTM! Proper agent initialization fix.

The explicit await agent.initialize() call correctly addresses the bug described in LCORE-470. The placement is optimal - immediately after agent creation and before any subsequent operations that depend on the agent being fully initialized. This ensures the agent is properly set up before session management or any potential reuse scenarios.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[maorfr]

/lgtm

[maorfr]

possibly related to #317

[tisnik]

LGTM

[eranco74]

Thanks!!