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

pubsub: add optional check for leaked messages #563

Closed
jba opened this issue Mar 16, 2017 · 1 comment
Closed

pubsub: add optional check for leaked messages #563

jba opened this issue Mar 16, 2017 · 1 comment
Assignees
Labels
api: pubsub Issues related to the Pub/Sub API. help wanted We'd love to have community involvement on this issue. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@jba
Copy link
Contributor

jba commented Mar 16, 2017

Bryan Mills suggests using a finalizer to check for messages that have not been acked:

In ReceiveSettings:

// ReportLeakedMessage is called in a finalizer if a message
// passed to Receive becomes unreachable without any calls to
// its Ack or Nack methods.
//
// If ReportLeakedMessage is nil, then ….
ReportLeakedMessage func(*pubsub.Message)
@jba jba added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. api: pubsub Issues related to the Pub/Sub API. labels Mar 16, 2017
@jba jba added the help wanted We'd love to have community involvement on this issue. label Aug 22, 2017
@jba
Copy link
Contributor Author

jba commented Dec 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: pubsub Issues related to the Pub/Sub API. help wanted We'd love to have community involvement on this issue. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

1 participant