Open ElGranLoky opened 2 years ago
@amodelbello the proyect is still alive?
@amodelbello the proyect is still alive?
Hi @ElGranLoky - I wouldn't say it's dead, but the current maintainers of this project don't have the bandwidth to respond to PRs and issues from the community. I no longer work for Meow Wolf but I've been in communication with some of the engineers and know they're under a lot of pressure to get current projects to production. I don't think you'll see a response from them in the short term.
I would highly encourage you, or anyone who uses this code, to fork the repo and add their own fixes/features.
Would it be that much effort to merge this in?
I just wasted a significant amount of time trying to directly publish a message to a queue. Thanks to @ElGranLoky I now have a solution.
Hello,
I have seen that when an input node is generated, to send messages directly to a queue using the default exchange, it does not use the value of routingKey as the name of the queue and because of that the messages are lost due to routing failure.
From what I've seen, the value of replyTo can be used to make sending the message work correctly, but it doesn't seem intuitive to the user.
I haven't reviewed all the code and I don't know if the pull request is valid, but the tests I have done do not modify the normal operation and prevent the routingKey value from being used incorrectly.