-
Notifications
You must be signed in to change notification settings - Fork 554
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
Conflicting dependencies running scripts/eachdist.py develop #1248
Comments
Updated opentelemetry-python-contrib/exporter/opentelemetry-exporter-datadog/setup.cfg: allowed the script to run, but then running python3 scripts/eachdist.py test failed with: |
Updated instrumentation/opentelemetry-instrumentation-flask/src/opentelemetry/instrumentation/flask/package.py now rerunning eachdist.py develop fails with: ERROR: Cannot install opentelemetry-instrumentation-flask and opentelemetry-instrumentation-pyramid[test]==0.33b0 because these package versions have conflicting dependencies. The conflict is caused by: To fix this you could try to:
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts |
Updated instrumentation/opentelemetry-instrumentation-pyramid/setup.cfg now can run eachdist.py develop, but eachdist.py test fails with: ====================================================================== FAILURES ====================================================================== self = <tests.test_sqlalchemy.TestSqlalchemyInstrumentation testMethod=test_async_trace_integration>
instrumentation/opentelemetry-instrumentation-sqlalchemy/tests/test_sqlalchemy.py:114: /usr/lib/python3.8/asyncio/base_events.py:616: in run_until_complete cls = <class 'sqlalchemy.dialects.sqlite.aiosqlite.SQLiteDialect_aiosqlite'>
E ModuleNotFoundError: No module named 'aiosqlite' .venv/lib/python3.8/site-packages/sqlalchemy/dialects/sqlite/aiosqlite.py:313: ModuleNotFoundError self = <tests.test_sqlalchemy.TestSqlalchemyInstrumentation testMethod=test_create_async_engine_wrapper>
instrumentation/opentelemetry-instrumentation-sqlalchemy/tests/test_sqlalchemy.py:217: /usr/lib/python3.8/asyncio/base_events.py:616: in run_until_complete cls = <class 'sqlalchemy.dialects.sqlite.aiosqlite.SQLiteDialect_aiosqlite'>
E ModuleNotFoundError: No module named 'aiosqlite' .venv/lib/python3.8/site-packages/sqlalchemy/dialects/sqlite/aiosqlite.py:313: ModuleNotFoundError -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html |
While I expect the required change to the datadog exporter was simply an oversight as all others appear to be on 0.33b0, the other two changes I'm less certain of their impacts (though tests generally look ok) since they change the versions of flask and werkzeug. The last round of errors I haven't looked too deeply at. If this is all from some mistake on my part, my apologies, this is my first time attempting to clone and work with the project. |
Next step did the following two changes: instrumentation/opentelemetry-instrumentation-httpx/setup.cfg now it seems to have failures in test_elasticsearch.py and appears to freeze at: |
Just saw the first issue was captured here #1083 and it appears I'm beating down a no longer supported path. |
@droppedbars yes, please use |
Describe your environment
FWIW, on Mint 20.2 using Python 3.8.10
Steps to reproduce
Brand new clone and attempt to install the dependencies:
git clone https://github.com/open-telemetry/opentelemetry-python-contrib.git
cd ./opentelementry-python-contrib
python3 -m venv .venv
source ./.venv/bin/activate
python3 -m pip install --upgrade pip
python3 scripts/eachdist.py develop
What is the expected behavior?
Successful installation of dependencies
What is the actual behavior?
ERROR: Cannot install opentelemetry-exporter-datadog[test]==0.30b0, opentelemetry-instrumentation-aiohttp-client[test]==0.33b0, opentelemetry-instrumentation-aiopg[test]==0.33b0, opentelemetry-instrumentation-asgi==0.33b0, opentelemetry-instrumentation-asgi[test]==0.33b0, opentelemetry-instrumentation-asyncpg[test]==0.33b0, opentelemetry-instrumentation-aws-lambda[test]==0.33b0, opentelemetry-instrumentation-boto3sqs[test]==0.33b0, opentelemetry-instrumentation-boto[test]==0.33b0, opentelemetry-instrumentation-botocore[test]==0.33b0, opentelemetry-instrumentation-celery[test]==0.33b0, opentelemetry-instrumentation-dbapi==0.33b0, opentelemetry-instrumentation-dbapi[test]==0.33b0, opentelemetry-instrumentation-django[test]==0.33b0, opentelemetry-instrumentation-elasticsearch[test]==0.33b0, opentelemetry-instrumentation-falcon[test]==0.33b0, opentelemetry-instrumentation-fastapi[test]==0.33b0, opentelemetry-instrumentation-flask[test]==0.33b0, opentelemetry-instrumentation-grpc[test]==0.33b0, opentelemetry-instrumentation-httpx[test]==0.33b0, opentelemetry-instrumentation-kafka-python[test]==0.33b0, opentelemetry-instrumentation-pymemcache[test]==0.33b0, opentelemetry-instrumentation-pymongo[test]==0.33b0, opentelemetry-instrumentation-pyramid[test]==0.33b0, opentelemetry-instrumentation-redis[test]==0.33b0, opentelemetry-instrumentation-remoulade[test]==0.33b0, opentelemetry-instrumentation-requests[test]==0.33b0, opentelemetry-instrumentation-sqlalchemy[test]==0.33b0, opentelemetry-instrumentation-starlette[test]==0.33b0, opentelemetry-instrumentation-tornado[test]==0.33b0, opentelemetry-instrumentation-urllib3[test]==0.33b0, opentelemetry-instrumentation-urllib[test]==0.33b0, opentelemetry-instrumentation-wsgi==0.33b0, opentelemetry-instrumentation-wsgi[test]==0.33b0 and opentelemetry-test-utils because these package versions have conflicting dependencies.
The conflict is caused by:
opentelemetry-instrumentation-wsgi[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-sdk 1.12.0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-dbapi[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-asgi[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-botocore[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-django[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-wsgi 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-kafka-python[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-aws-lambda[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-tornado[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-pymemcache[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-urllib3[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-aiohttp-client[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-falcon[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-fastapi[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-asgi 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-boto[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-pyramid[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-redis[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-requests[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-boto3sqs[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-flask[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-pymongo[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-grpc[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-starlette[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-sqlalchemy[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-asyncpg[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-aiopg[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-dbapi 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-httpx[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-celery[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-remoulade[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-elasticsearch[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-instrumentation-urllib[test] 0.33b0 depends on opentelemetry-semantic-conventions==0.33b0
opentelemetry-exporter-datadog[test] 0.30b0 depends on opentelemetry-semantic-conventions==0.30b0
To fix this you could try to:
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
The text was updated successfully, but these errors were encountered: