Skip to content

fix: log warning on _extract_summaries exception instead of silent failure#6

Merged
mrjunos merged 1 commit into
mainfrom
fix/silent-exception-logging
Apr 8, 2026
Merged

fix: log warning on _extract_summaries exception instead of silent failure#6
mrjunos merged 1 commit into
mainfrom
fix/silent-exception-logging

Conversation

@mrjunos

@mrjunos mrjunos commented Apr 7, 2026

Copy link
Copy Markdown
Owner

Summary

_extract_summaries was catching all exceptions and returning "" with no log output. Any parse failure was invisible — the user would get a context-less LLM response with no indication of what went wrong.

Fix: log a WARNING with the exception message before returning "". Behavior is unchanged, failures are now visible.

Tests added (56 total, up from 53)

3 new unit tests for _extract_summaries:

  • Invalid JSON logs a warning and returns ""
  • Nested node summaries are extracted correctly
  • Empty nodes returns ""

Test plan

  • 56 tests passing
  • CI green

🤖 Generated with Claude Code

…_summaries

Previously, any parse failure returned "" with no indication of what
went wrong. Now logs a WARNING with the exception message so failures
are visible in logs without changing the fallback behavior.

Adds 3 unit tests for _extract_summaries: invalid JSON logs warning,
nested summaries extracted correctly, empty nodes returns "".

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mrjunos
mrjunos merged commit 6c78c7a into main Apr 8, 2026
1 check passed
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