Closed
Description
Run our test suites of the different integrations with the potel-base
branch. (Just ran tox -f aiohttp
for example on the potel-base
branch and made notes on the errors that occured)
- If the integration is checked
[X]
then all tests are green. XXX
means test suite is failing???
means are not run by tests for integrations (so no entry in tox.ini)
There is this PR that is configured to run all the test suites (and not break on the first failing test suite) where you can see the current state of affairs:
Integrations
AI:
- anthropic
- cohere
- langchain
- openai
- huggingface_hub
AWS:
- aws_lambda
Cloud:
- boto3
- chalice
- cloud_resource_context
- gcp
Common:
- common
DBs:
- asyncpg
- clickhouse_driver
- pymongo
- redis
- redis_py_cluster_legacy
- sqlalchemy (1 test failing, because we do not enforce the 1000 spans per transaction limit)
GraphQL:
- ariadne
- gql
- graphene
- strawberry
Misc:
- launchdarkly
- loguru
- openfeature
- opentelemetry
- potel
- pure_eval
- trytond
Network:
- gevent
- grpc (tests crash!, to many events)
- httpx (
'POTelSpan' object has no attribute '_span_recorder'
, wrong bread crumbs) - requests
Tasks:
- arq
- beam
- celery (Tests fail because of some import errors)
- dramatiq
- huey
- ray
- rq
- spark
Web 1:
- django
- flask
- starlette
- fastapi
Web 2:
- aiohttp
- asgi
- bottle
- falcon
- litestar
- pyramid
- quart
- sanic
- starlite
- tornado