Skip to content
This repository has been archived by the owner. It is now read-only.

/ release-services Archived

Use dedicated thread for webhook #2106

Closed
La0 opened this issue May 15, 2019 · 1 comment
Closed

Use dedicated thread for webhook #2106

La0 opened this issue May 15, 2019 · 1 comment
Assignees
@La0
Labels
app:pulselistener

Comments

@La0
Copy link
Contributor

@La0 La0 commented May 15, 2019

The webhook runs alongside other consumers (including the mercurial one), and sometimes fail unexpectedly, giving HTTP 500 errors to Phabricator. The build is then automatically marked as failed.

One of the fails here: it's just a simple Heroku 500
@La0 La0 self-assigned this May 15, 2019
@marco-c
Copy link
Collaborator

@marco-c marco-c commented May 15, 2019

We should make sure we're running them in separate threads.
La0 added a commit to La0/mozilla-relengapi that referenced this issue May 17, 2019
@La0
pulselistener: Run webserver in dedicated process, fixes mozilla#2106.
Verified
This commit was signed with the committer’s verified signature.
La0 Bastien Abadie
GPG key ID: F5F60CAA5BB69CAA Learn about vigilant mode.
151ad90
@La0 La0 mentioned this issue May 17, 2019
Merged
La0 added a commit to La0/mozilla-relengapi that referenced this issue May 20, 2019
@La0
pulselistener: Run webserver in dedicated process, fixes mozilla#2106.
Verified
This commit was signed with the committer’s verified signature.
La0 Bastien Abadie
GPG key ID: F5F60CAA5BB69CAA Learn about vigilant mode.
cb4ef7d
@La0 La0 closed this in #2112 May 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@La0 La0

Labels
app:pulselistener
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

Use dedicated process for webserver
2 participants
@La0 @marco-c