The last log entry I can find related to that bug shows a failure with OOPS-0bd919facf32dce985bf3dd2eea748ca, which starts as follows:
DisconnectionError: terminating connection due to administrator command
CONTEXT: SQL statement "UPDATE BugTaskFlat SET datecreated = NEW.datecreated, product = NEW.product, productseries = NEW.productseries, distribution = NEW.distribution, distroseries = NEW.distroseries, sourcepackagename = NEW.sourcepackagename, status = NEW.status, importance = NEW.importance, assignee = NEW.assignee, milestone = NEW.milestone, owner = NEW.owner, date_closed = NEW.date_closed WHERE bugtask = NEW.id"
PL/pgSQL function bugtask_maintain_bugtaskflat_trig() line 29 at SQL statement
ERROR: server conn crashed?
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
I think this is just a failure due to happening to run into a separate infrastructure bug that pops up from time to time but typically only lasts for about ten minutes, which suggests that it should work eventually. I'd leave it a few more days to see if it catches up, but otherwise file a new bug.
The last log entry I can find related to that bug shows a failure with OOPS-0bd919facf32dce985bf3dd2eea748ca, which starts as follows:
Disconnection Error: terminating connection due to administrator command
datecreated = NEW.datecreated,
product = NEW.product,
productseries = NEW.productseries,
distribution = NEW.distribution,
distroseries = NEW.distroseries,
sourcepackage name = NEW.sourcepacka gename,
status = NEW.status,
importance = NEW.importance,
assignee = NEW.assignee,
milestone = NEW.milestone,
owner = NEW.owner,
date_ closed = NEW.date_closed
WHERE bugtask = NEW.id" maintain_ bugtaskflat_ trig() line 29 at SQL statement
CONTEXT: SQL statement "UPDATE BugTaskFlat SET
PL/pgSQL function bugtask_
ERROR: server conn crashed?
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
I think this is just a failure due to happening to run into a separate infrastructure bug that pops up from time to time but typically only lasts for about ten minutes, which suggests that it should work eventually. I'd leave it a few more days to see if it catches up, but otherwise file a new bug.