You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
centos
RocketMQ version
develop
JDK Version
1.8
Describe the Bug
When the heartbeat is reported, the calling function only contains two modes: push/pull, so the judgment of pop consumption mode should be added to the logic of pushImpl, so that the correct consumption mode can be uploaded during the heartbeat
Steps to Reproduce
null
What Did You Expect to See?
null
What Did You See Instead?
null
Additional Context
No response
The text was updated successfully, but these errors were encountered:
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.
Runtime platform environment
centos
RocketMQ version
develop
JDK Version
1.8
Describe the Bug
When the heartbeat is reported, the calling function only contains two modes: push/pull, so the judgment of pop consumption mode should be added to the logic of pushImpl, so that the correct consumption mode can be uploaded during the heartbeat
Steps to Reproduce
null
What Did You Expect to See?
null
What Did You See Instead?
null
Additional Context
No response
The text was updated successfully, but these errors were encountered: