Skip to content

fix(getting_started): unpin 4.4.7 — validator ERROR is misleading but harmless#61

Merged
abhishekmishragithub merged 2 commits into
mainfrom
fix/unpin-447-keep-comment
Jun 11, 2026
Merged

fix(getting_started): unpin 4.4.7 — validator ERROR is misleading but harmless#61
abhishekmishragithub merged 2 commits into
mainfrom
fix/unpin-447-keep-comment

Conversation

@abhishekmishragithub

Copy link
Copy Markdown
Collaborator

Summary

Reverts PR #50's smallestai<4.4.7 pin. Re-verified end-to-end on smallestai==4.4.7: the new startup validator logs a scary ValueError: Session not initialized ERROR + traceback, but the pod still accepts sessions and the agent runs normally.

What I tested

python3 -m venv .venv
.venv/bin/pip install "smallestai==4.4.7" loguru python-dotenv
curl -sL .../cookbook/main.tar.gz | tar -xz --strip-components=2 .../getting_started
cd getting_started
OPENAI_API_KEY=sk-placeholder python server.py

Boot log:

ERROR Startup validation failed — pod will not accept sessions. ValueError: Session not initialized
INFO  Application startup complete.        ← server reaches ready state
INFO  Uvicorn running on http://0.0.0.0:8080

Real WebSocket handshake (via smallestai.cli.lib.chat.ChatClient):

✓ Connected and ready!
HANDSHAKE OK: True
Session complete

The validator phrase "pod will not accept sessions" is wrong in the log — the pod does accept sessions. It's a dry-run hook that calls user's setup_handler against a null WebSocket; every example's await session.start() raises during validation, but real connections work fine.

Why we pinned in the first place (and why it was wrong)

The pin in PR #50 came from a single observation that boot looked broken. I missed the Application startup complete. line a few lines below the ERROR. Bot review on the docs PR #164 (entelligence-ai) flagged the contradiction: pinning broke the parallel background_agent example (which needs SDKAgentLogEvent from 4.4.7). Net negative.

Changes

  • voice-agents/getting_started/requirements.txt: drop the <4.4.7 upper bound
  • Inline comment updated to describe the harmless validator log so customers don't file bugs

background_agent/requirements.txt already pinned >=4.4.7 (which is correct — it needs SDKAgentLogEvent); leaving as-is.

Test plan

  • cd voice-agents/getting_started && pip install -r requirements.txt resolves to latest smallestai>=4.4.6 (currently 4.4.7)
  • python server.py reaches "Application startup complete." (verified)
  • agent-crew chat connects + handshake completes (verified)

Companion docs PR

smallest-inc/smallest-ai-documentation PR (link incoming) — same revert + adds an explainer Warning in the Installation section.

… harmless

PR #50 pinned smallestai<4.4.7. Re-verified on smallestai==4.4.7:

  Boot log:
    ERROR Startup validation failed — pod will not accept sessions.
          ValueError: Session not initialized
    INFO  Application startup complete.
    INFO  Uvicorn running on http://0.0.0.0:8080

  Real handshake (via ChatClient): ✓ Connected and ready! Session complete.

The validator dry-runs setup_handler against a null WebSocket, always
trips on `await session.start()`, and prints the traceback at ERROR
level. The pod still accepts sessions and the agent runs normally.

Pinning <4.4.7 broke the parallel background_agent example (which needs
SDKAgentLogEvent from 4.4.7). Net negative.

Drop the upper bound; keep an inline comment explaining the noisy boot
log so customers don't file bugs.

Verification log: /Users/tunejedi/Projects/smallest_work/verifications/sprint-31-unpin-447.log
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
smallest-showcase Ready Ready Preview, Comment Jun 10, 2026 9:22pm

Request Review

…l voice

Drop conversational framing ('misleading', 'safe to ignore', 'works
despite the message'). State the routine, the log line, and that the
server continues. The underlying log-message wording is a separate
SDK concern; doc/example comments should describe observed behavior
technically, not editorialize.
@abhishekmishragithub
abhishekmishragithub merged commit d7abdc4 into main Jun 11, 2026
2 checks 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