-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(weave): Cleanup integrations tests and inline pydantic and dataclass objects #2260
Conversation
Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=f42b4a5636c83db1cd7d73d69c75a70c2bf3b250 |
abeb011
to
6e4b8e1
Compare
weave/integrations/groq/groq_test.py
Outdated
("groq.chat.completions.create", 1), | ||
("get_game_score", 1), | ||
("groq.chat.completions.create", 1), | ||
calls_list = [_get_op_name(c.op_name) for c in calls] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you remove the flatten calls? We are not only asserting order, but also depth. Those assertions are important, but lost here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see, I misunderstood what the index represented.
client.calls()
is already flat and doesn't have that nesting atm. Should there be an option for that?
("llama_index.templating", 2), | ||
("llama_index.llm", 2), | ||
("openai.chat.completions.create", 3), | ||
"llama_index.query", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here (and all other places this got dropped
fcb9292
to
dbb4c6f
Compare
Summary
client.calls()
instead of lower levelclient.server.calls_query()
api for tests
langchain
tests still use the lower level because the ordering is different there (seems to be BF?)integration_utilities.py