Skip to content

test: cover container serialization in messages - #94

Merged
peteski22 merged 3 commits into
mainfrom
feat/messages-container-continuity
Sep 25, 2026
Merged

peteski22 merged 3 commits into
mainfrom
feat/messages-container-continuity

Conversation

@HareeshBahuleyan

@HareeshBahuleyan HareeshBahuleyan commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Why

Container IDs must reach the gateway so callers can reuse containers across message requests.

This is a separate PR because codegen updates the generated client, while these hand-written regression tests verify container forwarding through the public sync and async SDK wrappers.

What changed

Add sync and async regression tests using the mocked anthropic:claude-5-sonnet model string. Sync the lockfile package version with pyproject.toml.

Notes

  • Rebased onto current main, which already includes container support; no generated code changes remain.
  • Validation: 141 unit tests passed; Ruff and mypy passed.

Include container in MessagesRequest serialization so sync and async message calls forward container IDs to the gateway.

Add regression tests covering both clients.
@HareeshBahuleyan HareeshBahuleyan changed the title fix: preserve container in messages requests test: cover container serialization in messages Sep 23, 2026
@HareeshBahuleyan
HareeshBahuleyan force-pushed the feat/messages-container-continuity branch from 79de4f1 to 943353c Compare September 23, 2026 12:16
@HareeshBahuleyan HareeshBahuleyan self-assigned this Sep 23, 2026
@peteski22
peteski22 merged commit da10abc into main Sep 25, 2026
3 checks passed
@peteski22
peteski22 deleted the feat/messages-container-continuity branch September 25, 2026 15:02
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.

2 participants