Page MenuHomePhabricator

Phabricator dump used by Phlogiston should be updated when Phabricator is upgraded
Closed, ResolvedPublic0 Estimated Story Points

Description

Omnibus task for updating Phabricator dumps used by Phlogiston when Phabricator is upgraded.

Event Timeline

JAufrecht assigned this task to chasemp.
JAufrecht raised the priority of this task from to Needs Triage.
JAufrecht updated the task description. (Show Details)
JAufrecht added a project: Phabricator.
JAufrecht added subscribers: JAufrecht, csteipp.

I don't know much about how the dump is generated - is it just excluding anything with a custom policy? That shouldn't break - policy is still stored the same way it's just user interface stuff that's changing for the most part.

chasemp added a subscriber: chasemp.

@mmodell it's just https://phabricator.wikimedia.org/diffusion/PHTO/browse/master/public_task_dump.py which is basically "find public tasks and dump them with associated public things"

I'm not involved w/ this ongoing now so I can't really keep track of the relation between upgrades and the dump well. but it's pretty sane ..I think

@JAufrecht: Upgrade happened. When you have time, please report if the dump broke. Or not. :) Thanks.

It seems to be fine this morning, but James points out that the migration of the points field might have happened after the dump? Let's give it one more day to be sure.

@JAufrecht: T127524#2050513 implies this task is invalid (nothing to fix)?

When I first checked it, I misread the dates by a few hours and I was still working pre-dump. It was broken from Thu to Sun, ran successfully Sunday. Let me spend another day or two checking before declaring this okay.

Some data is missing from the new Phlogiston reports; will need to investigate further.

Could you share which data (if you already have an overview)?

JAufrecht set the point value for this task to 0.Mar 11 2016, 7:19 PM
JAufrecht updated the task description. (Show Details)

It's not active. I find it helpful to coordinate all of the related issues when a new one comes up - should I re-open this with a new sub-task if that happens?

It's ok, I'll just unsubscribe. I've been monitoring this to be sure that the issue was resolved.

@JAufrecht: Is this still an issue / should this task remain open? Or do things work more reliably in these days?

It's been stable since August, after the db upgrade. However, it is useful to have all of the outage tasks linked together, e.g. via this parent task. Some options:

  1. leave as is. I assume having this task open is annoying, though.
  2. close this tracking task, and then I'll re-open it if there are new children
  3. Instead of using a parent task, use some other method such as a tag or column in a tag to relate these tasks to each other.

Removing Phabricator as there's nothing to do there.

Should we do #2 instead, leave this as Phabricator but close it?

JAufrecht claimed this task.

no active issues; closing this tracking task.