Some more information:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 26 2015
Nov 25 2015
Nov 24 2015
Sorry about the delay... here's the trace from running /bin/storage upgrade --namespace testT9773_$RANDOM --force --no-adjust --trace:
Gah, details of the Herald transcript have already been garbage collected.
Out pf curiosity, why not use the @{article:...} syntax instead of copy-pasting the full URL?
Nov 23 2015
Just wanted to clarify as I'm not entirely sure that I understand... So we currently have a puppet role named phabricator_worker which runs phd daemons. As a step in our puppet scripts, we basically run /usr/src/phabricator/bin/almanac register --device=worker.phabricator.example.com --private-key=/path/to/private.key.
Nov 22 2015
In T9784#145136, @andrask wrote:@joshuaspence what do you think about this issue?
("No time specified" in Phame is a bit odd too, but I think that's been fixed already)
Nov 21 2015
I'm assuming that @terrismotox is just playing around.
Nov 19 2015
For what it's worth, we have a very similar setup (40ish repositories in Phabricator, all hosted in Gitlab). We have not observed any performance issues such as those described in this ticket.
Nov 18 2015
Nov 17 2015
No, that's not currently possible, but it might be worth filing a Maniphest task for that.
Oh sorry... I am dumb.
Nov 16 2015
Ah sorry, I thought Almanac wasn't a prototype but Drydock was. I was mistaken though.
Nov 15 2015
On another note, why doesn't Almanac use Passphrase for key storage?
Fixed in rARC66ab1c955d27ff7875f62eb51a0bd6c4770a7ae3.
Nov 14 2015
Thanks, I spent ~10 minutes on it but couldn't figure it out.
Actually something weird is going on... I can't edit pastes either, even if the Edit Policy is set to "All Users".
I'm not sure how to fix this without adding pastePHID to PhabricatorFile, which doesn't feel like the best approach.
I started looking at this. It seems like the file attached to the Paste has a view policy of no-one, whereas it should probably inherit the view policy of the parent Paste.
Nov 13 2015
In the general case, this is impossible to resolve. Suppose that you had conflicting linter rules, such as one whiche enforced that files end with a newline character and another which enforces that files do not end with a newline character.
MySQL version is 5.6.27-0ubuntu1.
> time ./bin/storage upgrade --namespace testT9773 --force --no-adjust Loading quickstart template... Applying patch 'phabricator:db.xhpast'... Applying patch 'phabricator:20150906.mailinglist.sql'... Applying patch 'phabricator:20150930.drydock.log.1.sql'... Applying patch 'phabricator:20151001.drydock.rname.1.sql'... Applying patch 'phabricator:20151002.dashboard.status.1.sql'... Applying patch 'phabricator:20151002.harbormaster.bparam.1.sql'... Applying patch 'phabricator:20151009.drydock.auth.1.sql'... Applying patch 'phabricator:20151010.drydock.auth.2.sql'... Applying patch 'phabricator:20151013.drydock.op.1.sql'... Applying patch 'phabricator:20151023.harborpolicy.1.sql'... Applying patch 'phabricator:20151023.harborpolicy.2.php'... Applying patch 'phabricator:20151023.patchduration.sql'... Applying patch 'phabricator:20151030.harbormaster.initiator.sql'... Applying patch 'phabricator:20151106.editengine.1.table.sql'... Applying patch 'phabricator:20151106.editengine.2.xactions.sql'... Applying patch 'phabricator:20151106.phame.post.mailkey.1.sql'... Applying patch 'phabricator:20151106.phame.post.mailkey.2.php'... Applying patch 'phabricator:20151107.phame.blog.mailkey.1.sql'... Applying patch 'phabricator:20151107.phame.blog.mailkey.2.php'... Applying patch 'phabricator:20151108.phame.blog.joinpolicy.sql'... Applying patch 'phabricator:20151108.xhpast.stderr.sql'... Applying patch 'phabricator:20151109.phame.post.comments.1.sql'... Applying patch 'phabricator:20151109.repository.coverage.1.sql'... Applying patch 'phabricator:20151109.xhpast.db.1.sql'... Applying patch 'phabricator:20151109.xhpast.db.2.sql'... Applying patch 'phabricator:20151110.daemonenvhash.sql'... Storage is up to date. Use 'storage status' for details. Declining to apply storage adjustments.
This is the only thing that is blocking me from migrating all of our repositories from Gitlab to Phabricator. Is there a clear path forward here? If so, I could potentially work on this.
One thing I noticed is that I have a large number of test databases locally.
Here is a profile from running ManiphestTaskTestCase only (and without coverage): https://secure.phabricator.com/xhprof/profile/PHID-FILE-fkx2c4q3wtfn6cetww6s/
See https://secure.phabricator.com/xhprof/profile/PHID-FILE-jfpnkcj4lvtjwojxmttl/, which shows the profile from running arc unit --everything.
Right, I see. I had darkconsole.always-on enabled.
I'm not concern ed from a security point of view... I'd just rather not give people functionality that they don't need. Specifically, I'm sure someone will open DarkConsole by mistake and not know how to close it.
In T7053#144095, @epriestley wrote:This also seems to work properly on this host, although I hit the "daemons are not running" setup warning once, presumably by racing their restart. If this is an issue we can tweak how that warning works, I think.
Nov 12 2015
Running on a local MySQL server... I'll try to profile the tests later.