Thanks. That works.

We have a relatively small number of projects, so I just proceeded with the manual edit -> save approach.

My knowledge of unicode isn't up-to-scratch, but the symbol in question is \u1F4E7, presumably this is outside of BMP.

Yes, you are correct. This was likely caused by the if ($repository->getDetail('herald-disabled')) { return; } logic.

I think I have discovered the cause here... I had the owners application uninstalled, which means that the PhabricatorRepositoryCommitOwnersWorker tasks weren't being queued... and I'm guessing that as a result the PhabricatorRepositoryCommitHeraldWorker tasks weren't being queued either?

It seems that this issue also affections Maniphest, as I could not include unicode characters from the output of ./bin/phd debug task (instead, I replaced the unicode characters with ???).

I'm not hitting an issue, I would just like a more sane way to tell Phabricator what daemons should be launched on phd start.

I have a similar request. Personally, I feel that the phd.start-taskmasters configuration could be replaced with a more general phd.start-daemons configuration, which would list all of the daemons that are to be launched on ./bin/phd start.

(Submitted twice... whoops)

Actually, it looks like this is happening on your install as well. See https://secure.phabricator.com/project/view/3/.

Fair enough.

✘ Merged into T4710.

◀ Merged tasks: T4716.

Yeah that's right, the script continues executing.

Ok, thanks for your help.

Should I also delete the edges?

Awesome, this seems to work. Thanks!

Ok sure.

It seems that the commit still exists in the phabricator_differential.differential_commit table.

Ok, so the script works now, and the edge gets deleted. But the "Unknown Object (Commit)" still appears in the differential.

Ok, so I used the script you provided by modified it slightly to perform a dry run. However, I am getting the following error:

Thanks, I'll give that a try.

Closed by commit rARCa2706f653944.

SSH would definitely be a better solution. Looking forward to T550.

TBH, I didn't realise Conduit supported SSH... I will look into this a bit more first.

IMO, that'd be a better solution. But I think others will disagree internally.

Yeah this is what we do currently but its a hassle when dealing with multiple projects with the same credentials.

Closed by commit rARCef598794a812.

Thinking about it more, I think that your expectation is reasonable.

Closed by commit rPHU1aa6299fcdfb.