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.

Sign up for GitHub

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

Jump to bottom

fix ack_deadline_timeout in pubsub_cli #64

Closed
willkg opened this issue Dec 5, 2024 · 0 comments
Closed

fix ack_deadline_timeout in pubsub_cli #64

willkg opened this issue Dec 5, 2024 · 0 comments
Assignees
@willkg

Comments

@willkg
Copy link
Contributor

willkg commented Dec 5, 2024 •
edited
Loading

In bug 1912979, I was wrestling with the local dev environment for Socorro reprocessing the same crash reports over and over again. It's because the subscriptions were being created with the default ack deadline timeout of 10 seconds which isn't long enough.

This PR fixed it in Socorro: mozilla-services/socorro#6689

The fix in that PR was lost when we switched to obs-common.

We need to re-apply that PR and then update obs-common in Socorro.
@willkg willkg self-assigned this Dec 6, 2024
willkg added a commit that referenced this issue Dec 6, 2024
@willkg
Set ack_deadline_timeout for subscriptions (#64)
168350a 
This re-implements the fix from
mozilla-services/socorro#6689

Before this fix, the ack_deadline_timeout is 10 seconds which isn't long
enough for the Socorro processor to process a crash report which causes
the crash id to be available in the subscription again which causes the
crash report to get reprocessed over and over again.
github-merge-queue bot pushed a commit that referenced this issue Dec 6, 2024
@willkg
Set ack_deadline_timeout for subscriptions (#64) (#65)
ed18968 
This re-implements the fix from
mozilla-services/socorro#6689

Before this fix, the ack_deadline_timeout is 10 seconds which isn't long
enough for the Socorro processor to process a crash report which causes
the crash id to be available in the subscription again which causes the
crash report to get reprocessed over and over again.
@willkg willkg closed this as completed Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@willkg willkg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@willkg