Can't agree more.
This is unfortunate...

(2) would be good. Just as you note, replying to old commits is already broken anyway...

You were right, a few hour later, the it seems that all outstanding tasks had been failed, and the restarts stopped.

Yes, I'm certainly going to take my responsibility for that... (Though, maybe the command to delete repositories shouldn't be given completely in clear in the web-interface. As that likely made it sligthly easier to disregard the scary skull prompt...)

Hm, quite likely, yes...

@epriestley well, yes they do restart again. Just to fail once again on a new commit. Which basically means that I'm constantly having the banner of an unresolved setup issue (as no daemons are currently running).

Hm, looking closer at the trace above, it looks like phabricator is still trying to parse some SVN commit messages, PhabricatorRepositorySvnCommitMessageParserWorker. How can I completely wipe out all traces of this repository, as it seems that the removal above wasn't enough.
`

Has anybody heard of someone migrating jira issues to phabricator? We're thinking about doing that, and of there were some example scripts for the import to start with, that Spaulding be great.