We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Python
Ubuntu
python 3.12 rocketmq-python-client 5.0.1 阿里云消息队列 RocketMQ 5.0 最新版
No response
normal producer 发送的message id 总是加个01在前面,但是simple_comsumer 拉取的又没有这个01,导致ack失败,手动给message_id 加了01 后ack成功
normal producer 和 simple consumer 两个客户端,调试即可复现
...
The text was updated successfully, but these errors were encountered:
5.0.2修复了这个问题
Sorry, something went wrong.
This issue is stale because it has been open for 30 days with no activity. It will be closed in 3 days if no further activity occurs.
No branches or pull requests
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
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
Ubuntu
RocketMQ Version of the Client/Server
python 3.12
rocketmq-python-client 5.0.1
阿里云消息队列 RocketMQ 5.0 最新版
Run or Compiler Version
No response
Describe the Bug
normal producer 发送的message id 总是加个01在前面,但是simple_comsumer 拉取的又没有这个01,导致ack失败,手动给message_id 加了01 后ack成功
Steps to Reproduce
normal producer 和 simple consumer 两个客户端,调试即可复现
What Did You Expect to See?
...
What Did You See Instead?
...
Additional Context
...
The text was updated successfully, but these errors were encountered: