feat: Add Phoenix tracing integration #912
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… an example, and tests.
MichaelMcCulloch-deepsense-ai
requested review from
dazy-ds,
jakubduda-dsai and
mhordynski
Contributor
|
Code Coverage SummaryDetailsDiff against mainResults for commit: 372be04 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add libraries whitelist because otherwise checks do not pass. Tests
uv run pytest packages/ragbits-core/tests/unit/audit/test_phoenix.py
/Users/michael/Development/ragbits/.venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py:208: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"
warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
==================== test session starts =====================
platform darwin -- Python 3.11.11, pytest-8.3.3, pluggy-1.5.0
rootdir: /Users/michael/Development/ragbits/packages/ragbits-core
configfile: pyproject.toml
plugins: asyncio-0.24.0, cov-5.0.0, repeat-0.9.4, postgresql-7.0.1, anyio-4.9.0, rerunfailures-12.0, deepeval-2.9.7, xdist-3.8.0, logfire-3.19.0, hydra-core-1.3.2
asyncio: mode=Mode.AUTO, default_loop_scope=None
collected 4 items
packages/ragbits-core/tests/unit/audit/test_phoenix.py . [ 25%]
... [100%]Running teardown with pytest sessionfinish...
===================== 4 passed in 0.05s ======================