search

streadway / amqp

Go client for AMQP 0.9.1
http://godoc.org/github.com/streadway/amqp
BSD 2-Clause "Simplified" License
4.88k stars 621 forks source link

Exporting IsClosed for Channel #486

Closed eibrunorodrigues closed 2 years ago

eibrunorodrigues commented 3 years ago

I needed to access the Channel status on a project that I'm participating in. So, I just made the "closed" field public on channel.go in the same way as it is on connection.go. Nothing too fancy, but I think it is important to get the actual status of the channel.

Something that we have on RabbitMQ's client on Python (pika) and .Net (RabbitMQ) and I missed here.

Hope this helps, Best regards.

ianrocha commented 3 years ago

I'm having the same problem, can someone pls merge that PR?

dwdcth commented 3 years ago

Same problem too

michaelklishin commented 3 years ago

Hey folks,

I'm posting this on behalf of the core team.

As you have noticed, this client hasn't seen a lot of activity recently. Many users are unhappy about that and we fully recognize that it's a popular library that should be maintained more actively. There are also many community members who have contributed pull requests and haven't been merged for various reasons.

Because this client has a long tradition of "no breaking public API changes", certain reasonable changes will likely never be accepted. This is frustrating to those who have put in their time and effort into trying to improve this library.

We would like to thank @streadway for developing this client and maintaining it for a decade — that's a remarkable contribution to the RabbitMQ ecosystem. We this now is a good time to get more contributors involved.

Team RabbitMQ has adopted a "hard fork" of this client in order to give the community a place to evolve the API. Several RabbitMQ core team members will participate but we think it very much should be a community-driven effort.

What do we mean by "hard fork" and what does it mean for you? The entire history of the project is retained in the new repository but it is not a GitHub fork by design. The license remains the same 2-clause BSD. The contribution process won't change much (except that we hope to review and accept PRs reasonably quickly).

What does change is that this new fork will accept reasonable breaking API changes according to Semantic Versioning (or at least our understanding of it). At the moment the API is identical to that of streadway/amqp but the package name is different. We will begin reviewing PRs and merging them if they make sense in the upcoming weeks.

If your PR hasn't been accepted or reviewed, you are welcome to re-submit it for rabbitmq/amqp091-go. RabbitMQ core team members will evaluate the PRs currently open for streadway/amqp as time allows, and pull those that don't have any conflicts. We cannot promise that every PR would be accepted but at least we are open to changing the API going forward.

Note that it is a high season for holidays in some parts of the world, so we may be slower to respond in the next few weeks but otherwise, we are eager to review as many currently open PRs as practically possible soon.

Thank you for using RabbitMQ and contributing to this client. On behalf of the RabbitMQ core team, @chunyilyu and @michaelklishin.

eibrunorodrigues commented 3 years ago

Hey @michaelklishin,

Thank you so much for the updates, I'd just re-submitted the PR on the new repository 😃

For those who still want this feature, here's the link for us to discuss 😄

https://github.com/rabbitmq/amqp091-go/pull/4