feat: add Arize Phoenix tracing integration#904
feat: add Arize Phoenix tracing integration#904MichaelMcCulloch-deepsense-ai wants to merge 16 commits intodevelopfrom
Conversation
Code Coverage SummaryDetailsDiff against mainResults for commit: 8bd7d0a Minimum allowed coverage is ♻️ This comment has been updated with latest results |
| phoenix = [ | ||
| "arize-phoenix>=4.0.0,<5.0.0", | ||
| "openinference-instrumentation>=0.1.0,<1.0.0", | ||
| ] |
There was a problem hiding this comment.
Why are the range constraints so restrictive? uv uses >=4.36.0 by default
There was a problem hiding this comment.
12.0.0; 0.1.41
There was a problem hiding this comment.
Please update uv.lock accordingly
| # /// script | ||
| # requires-python = ">=3.10" | ||
| # dependencies = [ | ||
| # "ragbits-core[phoenix]", |
There was a problem hiding this comment.
Maybe it will be good to have constraint for the version where this extras will be available
There was a problem hiding this comment.
And which version would that be?
There was a problem hiding this comment.
I think it will be included in the next release which is 1.4.0 . Am I right @mhordynski ?
…le, and conditionally import openinference trace modules in tests.
Co-authored-by: Michal Pstrag <47692610+micpst@users.noreply.github.com>
…le, and conditionally import openinference trace modules in tests.
…le, and conditionally import openinference trace modules in tests.
…te usage for consistency.
|
resolving conflicts brought in a bunch of unrelated files. Should not have rebased. Moving to #912 |
No description provided.