Skip to content

chore(weave): remove experimental StainlessRemoteHTTPTraceServer#7185

Draft
andrewtruong wants to merge 1 commit into
masterfrom
andrew/sdk-uptake-00-remove-stainless-server
Draft

chore(weave): remove experimental StainlessRemoteHTTPTraceServer#7185
andrewtruong wants to merge 1 commit into
masterfrom
andrew/sdk-uptake-00-remove-stainless-server

Conversation

@andrewtruong

@andrewtruong andrewtruong commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Description

Removes the experimental StainlessRemoteHTTPTraceServer and all of its opt-in plumbing. The binding was already dormant on master: the weave_server_sdk dependency group it needs is commented out (it pinned a dead git generation of the SDK), and its CI matrix entries are disabled — a clean install could never actually use it.

The next PR in this stack (#7177) rebuilds RemoteHTTPTraceServer itself on the published weave-server-sdk, so the parallel class goes first:

  • weave/trace_server_bindings/stainless_remote_http_trace_server.py, its test file, the dormant stainless nox shard, and the commented-out CI matrix entries
  • the use_stainless_server setting, its weave.init docstring entry, and the stainless branch in init_weave_get_server
  • the --remote-http-trace-server pytest flag, the server_class fixture, the collection filter implementing the _remote/_stainless test-file split, and the now-meaningless remote_only/stainless_only markers
  • test_http_behavior_remote.pytest_http_behavior.py (pure rename; the suffix only existed to pair with _stainless)
  • the commented-out stainless dependency group in pyproject.toml and the AGENTS.md section documenting the flag
  • a stale docstring mention of the class in weave_client.py

No dependency or lockfile changes: the removed group was commented out, so resolution is untouched.

Testing

  • tests/trace_server_bindings — 55 passed (against the surviving RemoteHTTPTraceServer, no SDK installed)
  • import weave smoke test with weave-server-sdk absent from the env (proves no hidden dependency)
  • Full pre-push hook suite (ty, pyright, mypy, ruff check/format, fixit, typos) — all pass
  • Grep audit: zero remaining references to stainless / --remote-http-trace-server / use_stainless_server / the dead markers (excluding unrelated OpenAI-SDK "Stainless" header mentions)

The experimental stainless-generated binding is already dormant on master:
the weave_server_sdk dependency group it needs is commented out (it pinned
a dead git generation of the SDK), and its CI matrix entries are disabled.
The next PR in this stack rebuilds RemoteHTTPTraceServer itself on the
published weave-server-sdk, so the parallel class and all of its opt-in
plumbing go first:

- weave/trace_server_bindings/stainless_remote_http_trace_server.py, its
  test file, the dormant "stainless" nox shard, and the commented-out CI
  matrix entries
- the use_stainless_server setting, its weave.init docstring entry, and the
  stainless branch in init_weave_get_server
- the --remote-http-trace-server pytest flag, the server_class fixture, the
  collection filter implementing the _remote/_stainless test-file split, and
  the now-meaningless remote_only/stainless_only markers;
  test_http_behavior_remote.py is renamed to test_http_behavior.py (content
  unchanged) since the suffix only existed to pair with _stainless
- the commented-out stainless dependency group in pyproject.toml and the
  AGENTS.md section documenting the flag
- a stale docstring mention of the class in weave_client.py

andrewtruong commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator Author

@wandbot-3000

wandbot-3000 Bot commented Jun 11, 2026

Copy link
Copy Markdown

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