Skip to content

Limit stored responses; optimize status poll - #196

Open
tokebe wants to merge 1 commit into
mainfrom
storage-limit
Open

Limit stored responses; optimize status poll#196
tokebe wants to merge 1 commit into
mainfrom
storage-limit

Conversation

@tokebe

@tokebe tokebe commented Jul 27, 2026

Copy link
Copy Markdown
Contributor
  • Since humans rarely look at /asyncquery_status, logs are left out to avoid log retrieval overhead.
  • Responses are now only stored to a proportion, given that clients are not expected to retrieve responses outside of normal http response or async callback, we can limit storage to a sample for debugging purposes.

Since humans rarely look at /asyncquery_status, logs are left out to
avoid log retrieval overhead.
Responses are now only stored to a proportion, given that clients are
not expected to retrieve responses outside of normal http response or
async callback, we can limit storage to a sample for debugging purposes.
@codecov

codecov Bot commented Jul 27, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 40.00000% with 6 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/retriever/utils/mongo.py 20.00% 4 Missing ⚠️
src/retriever/query.py 33.33% 1 Missing and 1 partial ⚠️
Files with missing lines Coverage Δ
src/retriever/config/general.py 96.29% <100.00%> (+0.05%) ⬆️
src/retriever/utils/logs.py 45.87% <ø> (ø)
src/retriever/query.py 72.66% <33.33%> (+18.37%) ⬆️
src/retriever/utils/mongo.py 36.18% <20.00%> (-0.07%) ⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant