thune-xiaobai opened a new issue, #1015:
URL: https://github.com/apache/rocketmq-clients/issues/1015

   ### Before Creating the Bug Report
   
   - [x] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions).
   
   - [x] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq-clients/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [x] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Programming Language of the Client
   
   Python
   
   ### Runtime Platform Environment
   
   OS: mac 14.4
   Python version: CPython 3.13.4
   UV version: uv 0.7.12 (Homebrew 2025-06-06)
   
   
   
   ### RocketMQ Version of the Client/Server
   
   Client: 5.0.6
   
   ### Run or Compiler Version
   
   _No response_
   
   ### Describe the Bug
   
   wrong opentelemetry-exporter-otlp version 1.11.1 installed
   
   ### Steps to Reproduce
   
   reproduce cmd:
   uv add rocketmq-python-client
   
   output: 
   Using CPython 3.13.4 interpreter at: 
/usr/local/opt/[email protected]/bin/python3.13
   Creating virtual environment at: .venv
   Resolved 23 packages in 1.30s
   Prepared 2 packages in 1.01s
   Installed 22 packages in 44ms
    + backoff==1.11.1
    + certifi==2025.4.26
    + charset-normalizer==3.4.2
    + googleapis-common-protos==1.70.0
    + grpcio==1.73.0
    + grpcio-tools==1.73.0
    + idna==3.10
    + importlib-metadata==8.7.0
    + opentelemetry-api==1.34.1
    + opentelemetry-exporter-otlp==1.11.1
    + opentelemetry-exporter-otlp-proto-grpc==1.11.1
    + opentelemetry-exporter-otlp-proto-http==1.11.1
    + opentelemetry-proto==1.11.1
    + opentelemetry-sdk==1.34.1
    + opentelemetry-semantic-conventions==0.55b1
    + protobuf==6.31.1
    + requests==2.32.4
    + rocketmq-python-client==5.0.6
    + setuptools==80.9.0
    + typing-extensions==4.14.0
    + urllib3==2.4.0
    + zipp==3.23.0
   
   
   which adds default opentelemetry-exporter-otlp 1.11.1
   
   and when I try 
   ```python
   from rocketmq import Client
   ```
   
   raises error:
   ```
   >>> from rocketmq import Client
   Traceback (most recent call last):
     File "<python-input-3>", line 1, in <module>
       from rocketmq import Client
     File 
"/Users/xiaobai/gf/test_tmp/.venv/lib/python3.13/site-packages/rocketmq/__init__.py",
 line 18, in <module>
       from .v5.client import ClientConfiguration, Credentials
     File 
"/Users/xiaobai/gf/test_tmp/.venv/lib/python3.13/site-packages/rocketmq/v5/client/__init__.py",
 line 16, in <module>
       from .client import Client
     File 
"/Users/xiaobai/gf/test_tmp/.venv/lib/python3.13/site-packages/rocketmq/v5/client/client.py",
 line 26, in <module>
       from rocketmq.v5.client.metrics import ClientMetrics
     File 
"/Users/xiaobai/gf/test_tmp/.venv/lib/python3.13/site-packages/rocketmq/v5/client/metrics/__init__.py",
 line 16, in <module>
       from .client_metrics import ClientMetrics
     File 
"/Users/xiaobai/gf/test_tmp/.venv/lib/python3.13/site-packages/rocketmq/v5/client/metrics/client_metrics.py",
 line 19, in <module>
       from opentelemetry.exporter.otlp.proto.grpc.metric_exporter import \
           OTLPMetricExporter
   ModuleNotFoundError: No module named 
'opentelemetry.exporter.otlp.proto.grpc.metric_exporter'
   ```
   
   ### What Did You Expect to See?
   
   install correct dependency.
   
   ### What Did You See Instead?
   
   -
   
   ### Additional Context
   
   Temp fix:
   Add opentelemetry-exporter-otlp explicitly first. then add rocketmq client.
   which will have  opentelemetry-exporter-otlp==1.34.1 works correctly.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to