Skip to content

fix(composer): define module logger — NameError on group MCP stop failure#197

Merged
ShotaroKataoka merged 1 commit into
mainfrom
fix/composer-logger
Jul 8, 2026
Merged

fix(composer): define module logger — NameError on group MCP stop failure#197
ShotaroKataoka merged 1 commit into
mainfrom
fix/composer-logger

Conversation

@ShotaroKataoka

Copy link
Copy Markdown
Contributor

Summary

  • agent/modes/separated/composer.py calls logger.warning() in the run_group finally block (per-group MCP stop failure path) but never defined logger — the warning itself raised NameError.
  • Adds the standard logging.getLogger("sdpm.agent") module logger (same convention as factory.py / session.py / streaming.py).

Background

Found while investigating roadmap 3-4 (compose checkpoint resume). 3-4 itself was closed as won't-do: the deck workspace already persists slides/*.json on write, so the workspace itself is the checkpoint; group failures are covered by the #193 structured-error retry flow. Rationale recorded in the roadmap spec notes (local ledger).

Test

  • make lint / make test — 251 passed, 1 skipped

…lure

The finally block at run_group exit calls logger.warning() when the
per-group MCPClient fails to stop, but composer.py never defined
`logger` — the warning path itself raised NameError instead of
logging.
@ShotaroKataoka ShotaroKataoka added the blog:skip ブログ対象外 label Jul 8, 2026
@ShotaroKataoka ShotaroKataoka merged commit bd14394 into main Jul 8, 2026
12 of 13 checks passed
@ShotaroKataoka ShotaroKataoka deleted the fix/composer-logger branch July 8, 2026 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blog:skip ブログ対象外

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant