-
Notifications
You must be signed in to change notification settings - Fork 72
the topic_pah problem #52
Comments
Thank you for your time. Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes two things:
We get at least a dozen of questions through various venues every single day, often quite light on details. Getting all the details necessary to reproduce an issue, make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Our team is multiple orders of magnitude smaller than the RabbitMQ community. Please help others help you by providing a way to reproduce the behavior you're
Feel free to edit out hostnames and other potentially sensitive information. When/if we have enough details and evidence we'd be happy to file a new issue. Thank you. |
|
@michaelklishin I see.Thank you very much! |
I found that this topic_path has never been called.
I think it should be called when exchange has routingkey binding,but when binding routingkey did not be called.
Can you help me? I can't find the problem.
The text was updated successfully, but these errors were encountered: