- User Since
- Jan 8 2016, 11:11 PM (115 w, 10 h)
Thu, Mar 22
Fri, Mar 16
This is a buff to API humor
Fri, Mar 2
Feb 8 2018
Nov 7 2017
The harbormaster builds that we have running on revision creation can sometimes be rather slow; they're builds in our primary CI system, but with less of a priority than jobs in the submit queue. This will result in 10-30 minute delays for every revision in our monorepo. I understand the preference for only adding configuration settings when absolutely necessary, but since this may result in a significant time sink for any installs with expensive builds, is it worth keeping something around like differential.initial-state?
Aug 29 2017
Jul 21 2017
Jul 19 2017
In the refcursor table, our current autoincrement is at 312,036,016. This is only 7% of the way to int unsigned, but the fact that we've made it to 7% in 18 months might suggest that column should be BIGINT, unless there are performance impacts of that.
Jul 12 2017
+1, we've also had a handful of users request this as a per-user preference.
Jul 11 2017
Jul 6 2017
This information may be entirely useless, but it is somewhat related. We have a large number of repositories, with multiple clusters so this affects us in a major way.
Jul 3 2017
If you go through the process manually with the web UI, are the versions OK after initial creation? After adding an observed URI?
Jun 14 2017
May 23 2017
screenshot on ambien
May 17 2017
Do you bucket style guide violations with lint issues? While I obviously can't post internal reviews, I can give you a hand-waving indication that a non-zero percentage of comments are style-related things that aren't caught by linters.
Apr 26 2017
Really a very very beautiful hovercard. It's going to be great. Fantastic job. Really really proud of this hovercard.
Apr 21 2017
That was unclear: we can parameterize on lots of things, just not the commit hash, which is conceivably what you want us to parameterize on.
I have a related question regarding this quote:
Apr 20 2017
I agree, pagination way below the fold is rather inconspicuous
Bystander input: try page 3: https://phabricator.kde.org/source/krita/browse/master/libs/ui/?offset=200
Apr 10 2017
Mar 28 2017
pollice lock us in prisun.
Mar 27 2017
Mar 24 2017
FWIW, All packages in our monorepo have weak dominion.
How do we envision these rules applying to the following situation?
Mar 14 2017
Do git ls-remote (which, curiously, seems to be significantly faster than git fetch even when git fetch is a no-op).
Mar 9 2017
The default -- PhabricatorMailImplementationPHPMailerLiteAdapter
Feb 24 2017
@pouyana Here's a workaround for you. In your notification.servers Phabricator configuration, add path: "/ws/" to the client server. Then, modify your apache configuration like so:
Feb 14 2017
Jan 27 2017
This has come up again with a slightly different use case. We want to intelligently purge tags from our staging areas. To do this, we examine refs/tags/* in the staging area, and parse out the diff IDs. It would be great if we could do this from differential.revision.search, but the attachments/constraints don't support it. The current working approach is differential.querydiffs with the IDs, parse the revision IDs out, then differential.query to get the revision statuses and their associated diffs list. This approach allows us to make significantly less queries than examining *all* closed/abandoned revisions, then calling the frozen/deprecated differential.query for the diff list.
Jan 19 2017
Jan 13 2017
Awesome. Things appear to be working now. I suppose I can strip out all the overrides that the most recent commit stripped out. Sweetness.
so if isFieldEditable and isTemplateField are both false, will the field still show up in getcommitmessage?
Awesome. What do you think the time delta will be between release promotion and the fix you have being merged to master?
Jan 12 2017
shouldAppearInCommitMessage() is marked as obsolete, but still seems necessary for me to implement a CustomField that behaves as follows:
Nov 22 2016
Aug 30 2016
Aug 12 2016
After merging with upstream, we were able to increase our taskmasters up to 32, and still not come anywhere close to the number of connections that were previously used. So far, so good on our end.