Skip to content

Conversation

marco-c
Copy link
Collaborator

@marco-c marco-c commented Dec 3, 2019

Fixes #20

I'm not 100% sure, but I think we should do this.
The disadvantage is that when we e.g. pause code-review or code-coverage the queue will be killed and so we will miss some events;
The big advantage is that we will not cause queues to overgrow (the queues we are using are especially prone to overgrowing, even a few minutes of pause could mean a huge queue).

@marco-c marco-c requested a review from La0 December 3, 2019 15:34
@La0
Copy link
Contributor

La0 commented Dec 3, 2019

What's the harm in overgrowing queues, especially as they get auto deleted by the server after 20k messages ?

I don't feel comfortable enabling this in production for code review...

@marco-c
Copy link
Collaborator Author

marco-c commented Dec 3, 2019

What's the harm in overgrowing queues, especially as they get auto deleted by the server after 20k messages ?

It has caused tree closures in the past, it causes problems for the publisher.

I don't feel comfortable enabling this in production for code review...

We haven't even enabled the listening for code review yet, so this can't cause any problem there :P

@marco-c
Copy link
Collaborator Author

marco-c commented Dec 3, 2019

(let's not merge this yet as we decide in the near future what to do)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unbind pulse queues on teardown

2 participants