chore(weave): Further split out Query/Trace #2182
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Do not merge until after weave
0.50.15
release!Corresponding change in core: https://github.com/wandb/core/pull/23467
weave/legacy/
weave/
wandb_api
storage
,urls
,context_state
,artifact_fs
, and some stuff for fastapiweave/tests/
(for trace), orweave/legacy/tests/
(for legacy)mypy.ini
is split into trace and legacyTop-level requirements now reflect just the trace code -- legacy requirements moved to-- Deferred to simplify this PRweave/legacy/requirements.*
mypy.ini
broken out for trace and legacy respectivelyReview suggestions
Missing pieces (too hard atm):
conftest.py
weave_server.py
weave_server.sh
weave-js/
frontend/
trace_server/
integration_test/