This message is still being sent. You can check yourself by using this direct link for [Pulse Inspector](https://tools.taskcluster.net/pulse-inspector?bindings%5B0%5D%5Bexchange%5D=exchange%2Ftaskcluster-queue%2Fv1%2Ftask-group-resolved&bindings%5B0%5D%5BroutingKeyPattern%5D=%23) and "Start Listening". After a few seconds, you should see a lot of duplicates with the routing key `primary.SIlcBZkkT3e-8ZFxVK4nwQ.comm-level-1._`. This is the first time in months we see that happening on that queue. I initially thought it was due to a bug on our side (Python client listening to pulse events for code coverage builds), but it looks like it's on the pulse server side...
Bug 1582376 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This message is still being sent. You can check yourself by using this direct link for [Pulse Inspector](https://tools.taskcluster.net/pulse-inspector?bindings%5B0%5D%5Bexchange%5D=exchange%2Ftaskcluster-queue%2Fv1%2Ftask-group-resolved&bindings%5B0%5D%5BroutingKeyPattern%5D=%23) and "Start Listening". After a few seconds, you should see a lot of duplicates with the routing key `primary.SIlcBZkkT3e-8ZFxVK4nwQ.comm-level-1._`. This is the first time in months we see that happening on that queue. I initially thought it was due to a bug on our side (Python client listening to pulse events for code coverage builds), but it looks like it's on the pulse server side... Our code coverage generation is slowed down a lot because of this bug. - [Github issue on our side](https://github.com/mozilla/code-coverage/issues/179) - Exchange concerned : `exchange/taskcluster-queue/v1/task-group-resolved` on topic `#`