Skip to content
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

topic with namespace and retry is block #933

Closed
0daypwn opened this issue Oct 10, 2022 · 0 comments
Closed

topic with namespace and retry is block #933

0daypwn opened this issue Oct 10, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@0daypwn
Copy link
Contributor

0daypwn commented Oct 10, 2022

BUG REPORT

  1. Please describe the issue you observed:

    • What did you do (The steps to reproduce)?

    • What did you expect to see?

    • What did you see instead?
      [ISSUE #926] don't share limit channel in pushConsumer #923 add some code.
      example. topic name is test-topic
      when do subscribe, pc.crCh only add key: test-topic
      it does not include:
      a. topic with namespace. topic name is namespace%test-topic
      b. consumer retry topic. %RETRY%group

when consumer, because pc.crCh does not include topic, it will block.

  1. Please tell us about your environment:

    • What is your OS?

    • What is your client version?

    • What is your RocketMQ version?

  2. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

0daypwn pushed a commit to 0daypwn/rocketmq-client-go that referenced this issue Oct 10, 2022
@ShannonDing ShannonDing added the bug Something isn't working label Oct 11, 2022
0daypwn pushed a commit to 0daypwn/rocketmq-client-go that referenced this issue Oct 11, 2022
0daypwn pushed a commit to 0daypwn/rocketmq-client-go that referenced this issue Oct 11, 2022
@0daypwn 0daypwn closed this as completed Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants