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

bug in NameSpaceUtil::formatNameServerURL #142

Closed
ifplusor opened this issue Apr 30, 2019 · 1 comment
Closed

bug in NameSpaceUtil::formatNameServerURL #142

ifplusor opened this issue Apr 30, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@ifplusor
Copy link
Contributor

The issue tracker is ONLY used for the CPP/C client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.

Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.

Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?
    call NameSpaceUtil::formatNameServerURL with "192.168.17.43:9876;192.168.17.44:9876" on mac return ".17.43:9876;192.168.17.44:9876" and start consumer failed. then, encounter segment fault when exit.

  • What did you expect to see?
    return "192.168.17.43:9876;192.168.17.44:9876"

  • What did you see instead?

  1. Please tell us about your environment:
  • What is your OS?
    macOS Mojave 10.14.4

  • What is your client version?

  • What is your RocketMQ version?

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

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

@ifplusor ifplusor changed the title NameSpaceUtil::formatNameServerURL error bug in NameSpaceUtil::formatNameServerURL Apr 30, 2019
@ShannonDing ShannonDing added the bug Something isn't working label May 10, 2019
@ShannonDing ShannonDing mentioned this issue May 10, 2019
Closed
ShannonDing pushed a commit that referenced this issue May 10, 2019
@ifplusor
Copy link
Contributor Author

ifplusor commented May 15, 2019

fixed by #143

hugoasdf pushed a commit to hugoasdf/rocketmq-client-cpp that referenced this issue Jun 30, 2019
…variable.

declare correct string::size_type by auto. (apache#143)
hugoasdf added a commit to hugoasdf/rocketmq-client-cpp that referenced this issue Jun 30, 2019
* [ISSUE apache#142] save string::find result into a string::size_type variable.

declare correct string::size_type by auto. (apache#143)

* batch issue

* Update: update network interface. (apache#60)

* update network interface.

- feature: use only one event loop for all TcpTransport.
- update: network components.

* remove boost mutex, timed_mutex and condition_variable in TcpRemotingClient, TcpTransport and ReponseFunture.
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

No branches or pull requests

2 participants