Skip to content

Https support and updated Readme#5

Merged
google-oss-prow[bot] merged 7 commits intokubeflow:mainfrom
SanthoshToorpu:main
Oct 6, 2025
Merged

Https support and updated Readme#5
google-oss-prow[bot] merged 7 commits intokubeflow:mainfrom
SanthoshToorpu:main

Conversation

@SanthoshToorpu
Copy link
Copy Markdown
Contributor

This PR features an updated readme and provision for usage with https as well as sockets

Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Copy link
Copy Markdown
Contributor

@franciscojavierarceo franciscojavierarceo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like we removed a lot of the pipeline code, was that on purpose?

@SanthoshToorpu
Copy link
Copy Markdown
Contributor Author

Yeah @franciscojavierarceo its like a compiled version of the code. So the python file is equivalent to what we have rn.......

@franciscojavierarceo
Copy link
Copy Markdown
Contributor

I don't see a compiled version of the code. I just see the files removed.

@SanthoshToorpu
Copy link
Copy Markdown
Contributor Author

Yeah the files that were removed are the compiled yaml from the python file so I thought why keep it.

However if the yaml makes sense I'll add it back

@franciscojavierarceo
Copy link
Copy Markdown
Contributor

we should keep all of it.

@SanthoshToorpu
Copy link
Copy Markdown
Contributor Author

Aight then I'll add em back

Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
Signed-off-by: SanthoshToorpu <toorpusanthosh@gmail.com>
@franciscojavierarceo
Copy link
Copy Markdown
Contributor

/lgtm
/approve

@google-oss-prow
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: franciscojavierarceo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [franciscojavierarceo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit 37dc2d7 into kubeflow:main Oct 6, 2025
2 checks passed
zong0728 added a commit to zong0728/docs-agent that referenced this pull request Mar 22, 2026
Implements GSoC 2026 Agentic RAG spec Requirement kubeflow#5:

  'Robust retry logic is a must for all tools. The agent implements
   exponential backoff with jitter for Vector DB retrievals and LLM
   API timeouts. If tools strictly fail, the agent is configured to
   transparently degrade, informing the user that Live code context
   is currently unreachable.'

Changes:
- shared/retry.py: reusable @with_retry decorator supporting both
  sync and async callables; uses AWS full-jitter strategy
  (random.uniform(0, delay)) to prevent thundering-herd on retry;
  exposes DEGRADED_RESULT sentinel string for LLM-visible outage
  messages
- server/app.py, server-https/app.py:
  * milvus_search: remove silent exception swallow; add @with_retry
    (3 attempts, base 1s, max 10s, factor 2x + jitter); encoder
    loaded once at module level via _get_encoder() singleton
  * execute_tool: offload blocking milvus_search to asyncio.to_thread
    (websocket server) and run_in_threadpool (FastAPI server) so the
    async event loop stays responsive under concurrent load; on retry
    exhaustion return DEGRADED_RESULT so LLM communicates the outage
    to the user instead of silently hallucinating from empty context

Signed-off-by: Shengzhong Guan <guan@cmu.edu>
Made-with: Cursor
zong0728 added a commit to zong0728/docs-agent that referenced this pull request Mar 22, 2026
Implements GSoC 2026 Agentic RAG spec Requirement kubeflow#5:

  'Robust retry logic is a must for all tools. The agent implements
   exponential backoff with jitter for Vector DB retrievals and LLM
   API timeouts. If tools strictly fail, the agent is configured to
   transparently degrade, informing the user that Live code context
   is currently unreachable.'

Changes:
- shared/retry.py: reusable @with_retry decorator supporting both
  sync and async callables; uses AWS full-jitter strategy
  (random.uniform(0, delay)) to prevent thundering-herd on retry;
  exposes DEGRADED_RESULT sentinel string for LLM-visible outage
  messages
- server/app.py, server-https/app.py:
  * milvus_search: remove silent exception swallow; add @with_retry
    (3 attempts, base 1s, max 10s, factor 2x + jitter); encoder
    loaded once at module level via _get_encoder() singleton
  * execute_tool: offload blocking milvus_search to asyncio.to_thread
    (websocket server) and run_in_threadpool (FastAPI server) so the
    async event loop stays responsive under concurrent load; on retry
    exhaustion return DEGRADED_RESULT so LLM communicates the outage
    to the user instead of silently hallucinating from empty context

Signed-off-by: Shengzhong Guan <guan@cmu.edu>
Made-with: Cursor
Signed-off-by: Shengzhong Guan <guan@cmu.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants