I'm not really sure this is actually useful given that every method is now named <application>.whatever and you can search by substring.

Sorry, apparently after running arc upgrade it no longer times out (although it does take a long time).

arcanist(head=master, ref.master=8f69a5c378c3), flarc(), phutil(head=master, ref.master=ff84abc7d857)

In T11699#195930, @chad wrote:

The error log says July

The error log says July

Server

• rP38b10f05a224d29c723c033dec0820f977aa8026
• rARC483e985d08d279816708a9e755de8e5c3586d3ba
• rPHU1a0371a2247a256d1e6e44d4f348adc2750a9788

version info please

Here are some query traces from XHProf:

Here are 2 use-cases which are both essentially the same in all the important ways:

Sort of. I'd like to have use cases (what are you trying to do?) first, and I'm not certain what the best representation of dates and times is for external consumption.

@epriestley: Are you open to patches that add more information to the calendar.event.search response? It currently does not even include the event time which is a pretty crucial detail to make the results useful.

@raincoastchris the context of this issue caught my eye because I've really wanted Phab to generate a cumulative flow chart and Kanban statistics for some time now. I took a stab at it today and modified an existing python script to generate a cumulative flow chart and Kanban statistics (https://github.com/lyahdav/analytics-limn-analytics-data/tree/kanban_stats) but configuring it is a bit painful because there is no easy way to get the names of all the columns in a workboard right now.

Feel free to submit a diff for this, should just involve adding some stuff to HarbormasterBuild in getFieldSpecificationsForConduit() and getFieldValuesForConduit().

We haven't received more information about this in more than a month.

I was looking for similar functionality (publish the state of some external system on a panel) and instead of updating the entire panel I think it would be nice to use Phlux or Paste:

Broadly, this isn't a use case we intend to support specifically. See T5873, T10363, T11330, T11563#192717 for some related discussion.

In T11530#192966, @chad wrote:

Maybe create a bot user called @shipit to trigger herald? Mentioning users CCs them to the object, but mentioning projects does nothing currently.

Maybe create a bot user called @shipit to trigger herald? Mentioning users CCs them to the object, but mentioning projects does nothing currently.

In T10456#184273, @jack.chung wrote:

if it helps anyone, the workaround "fix" is to place the following code in the file "src/applications/conduit/parametertype/ConduitBoolParameterType.php "

$value = (boolean) $value;

at about line 9 just before the following piece of code:

if (!is_bool($value)) {

Its a bit of a hack, so I'm not sure how much to trust this workaround for a production instance of Phabricator, but hopefully, it helps someone out there. The issue is (I think) basically related to http://stackoverflow.com/questions/27446946/preserve-data-type-of-post-fields-when-sending-data-using-php-and-curl where PHP converts the curl input as a string.

Follow PhabricatorSearchEngineExtension or similar.

If you only knew how lucky you are to have Evan explain this to you rather than trolling through grep -Rn "PhutilClassMapQuery" * --include \*.php errday.

(The second step is because some types of attachments work on multiple object types, and you could even conceivably write an "edge" attachment here that just works for anything and returns all edges, although I'm not confident that doing so isn't a major security problem.)

I think you've already written these, but the budget walkthrough is:

Live, armed, pre-commit A/B testing is unambiguously the most exciting part of our jobs.

For the record, I strongly endorse autopatching unreviewed code onto live, armed, autonomous combat vehicles.

Internal attachment is definitely the shortest path. Whatever we end up with is likely to look very similar to the naive version, and you can keep your attachment running after we offer an "edges" attachment, so there shouldn't be any real transition cost.

Should we implement this as an internal search attachment in the meantime? Or is there a possible pathway for @jcox to get something like this working in ~3 days?

This is basically a special case of T5873.

I'm thinking we just create a search attachment for maniphest.search which contains diff PHIDs.

Just want to +1 that this would be a very useful feature for us. I think our usecase is similar: We have a lot of teams (especially ops teams) using phab workboards and columns extensively. Rather than try to shoe horn different types of reporting, etc. into phab they are relying on external systems/tools, but it is pretty painful to extract data on what column tasks currently live in.

Herald firing on other things: T10109

Let's permanently destroy some data! This will introduce you to how to perform schema changes.

Awesome! I appreciate the quick fixes!

• This constraint should be fixed at HEAD of master. We just missed the deploy so it won't go until the cluster until next week (around August 20). Let me know if I missed anything.
• Empty constraints should be fixed at HEAD of master (they now error instead of being ignored).
• buildablePHID vs objectPHID confusion and inconsistencies should be fixed in the future by harbormaster.buildable.search. If you want a skeletal version of this now to reduce API tweaks later, let me know and we can get one in pretty easily.
• Linking to pre-filled forms seems maybe not hugely useful in practice, with some small risk of social engineering attacks? Feel free to file a separate request if you have use cases I'm not thinking of or whatever.

D16396 should make us raise a narrow error for "ids": [], "phids": [], "whateverPHIDs": [], etc., instructing you to pass a nonempty list.

I think fixing "ids":[] is trivial; it just works like that because we use the same Conduit type ("PHIDList") both for constraints and other things which can accept an empty array (like setting subscribers to [] to remove all the subscribers on an object).

(@yelirekim, just a heads up since whatever comes of this might impact you somehow.)

slightly related: there's some confusing naming in the result for harbormaster.querybuildables:

This also happens with integers and epochs:

@epriestley Is there a pathway for reading (not writing) edges which would be open to community contribution? Having arc patch Tnnnn functionality, pulling all the revisions attached to a particular task, would be really attractive for us as we tend to have a larger number of revisions per task.

Also, please note this:

Example 1: Batch edit of more projects at once - obviously easier to run script than having to click it manually.

In T11405#188030, @epriestley wrote:

How about this: we'll play the "5 whys" game described in Describing Root Problems to get to bottom of this problem. After we figure it out, you tell me why you didn't provide that information in the first place and how to improve the documentation so that it's clear what we're after. Sound good?

Fair enough. I'm totally willing to sprinkle my head with ashes after I'll find out what exactly is causing the misunderstanding of what "root cause" is. ;-) But not knowing it is obviously not helpful and leads to the same situation again.

How about this: we'll play the "5 whys" game described in Describing Root Problems to get to bottom of this problem. After we figure it out, you tell me why you didn't provide that information in the first place and how to improve the documentation so that it's clear what we're after. Sound good?

Come on, Evan, seriously? :-/

Please please please please please please please please please please please please read Describing Root Problems carefully and think about what it is asking for.