-
Notifications
You must be signed in to change notification settings - Fork 579
UN-3189 [MISC] Add whisper_hash logging in LLMWhisperer adapter extraction #1776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UN-3189 [MISC] Add whisper_hash logging in LLMWhisperer adapter extraction #1776
Conversation
WalkthroughRemoved a stray blank line in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
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. Comment |
unstract/sdk1/src/unstract/sdk1/adapters/x2text/llm_whisperer_v2/src/llm_whisperer_v2.py
Outdated
Show resolved
Hide resolved
…ction Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
f254d12 to
2c1a83a
Compare
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|
|



What
Why
request_idin log prefix provides correlation with the extraction operationHow
logger.info()call afterTextExtractionMetadatais created inLLMWhispererV2.process()Can this PR break any existing features. If yes, please list possible items. If no, please explain why.
Database Migrations
Env Config
Related Issues or PRs
Screenshot
Notes on Testing
Checklist
I have read and understood the Contribution Guidelines.