Yeah, there's no real hint about that in the UI to suggest that the box will update, and it's easy to miss since it looks nearly identical after it updates. I'll add a piece of hint text to hopefully make it more clear.

OH, that only happens if you do the human-readable option. I didn't notice that little box at the bottom had changed amidst the giant blob of json that the call returned.

Oh, maybe we could make this more clear. Here's how to use the examples to figure out how to make a call:

The good news though is with that hint I seem to have it working without even needing to POST: https://phabricator.myurl.com/api/differential.querydiffs?api.token=api-TOKEN&ids[0]=5

I can definitely try either of those two options, but to my point, it wasn't obvious to me from the documentation:

(Kicking Documentation off because this would just be another tab next to PHP / cURL / arc in Conduit, not static documentation.)

No, it would not.

Thanks for the hint!

Go to Conduit on your install.

Phrequent is a prototype application, and we don't provide support for these types of apps. Mostly it's expected that they will be incomplete and once we do move them to being officially supported they will have these features naturally (for example Conduit is "free" for any modern application.)

Is documentation available through other means than Conduit itself?

Phrequent is not installed on this server. Conduit only shows methods from installed applications.

Any ideas on how we can move forward with this?

OK weird, I can't reproduce it anymore. Anyway, I'll add the response body from differential.querydiffs here. It shouldn't contain any sensitive information, but I'll restrict the visibility of the file given that it does contain email addresses.

You can award and revoke badges from conduit, though we may build a more robust award api later.

I believe this was likely resolved by D16460. This (binary transport over Conduit) is still a problem in general, and T5955 is the general remedy, but diffusion.rawdiffquery specifically now returns data via Files.

Looks like search and edit are implemented, but not awards. Awarding a badge through conduit seems nice to have? but I don't see any requests for it, so not sure it's worth holding up unbeta.

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.

Thanks, D17218 should fix this.

We've formally frozen this method after D17158. The UI now encourages project.edit.

I'm going to merge this into T12074. Summarizing things so far and my short-term plans:

In T550#202580, @epriestley wrote:

Multiple hostname stuff: Today, the SSH hostname of an install and the HTTP hostname do not need to be the same.

We use this in the Phacility cluster: Phacility HTTP instances are at instance.phacility.com, but serve repositories via vault.phacility.com.

The technical reason for this is mostly that ELBs can't accept port 22 traffic -- or couldn't when I set them up. It looks like new VPC-ELBs may be able to accept on 22. We currently use HAProxy to balance SSH traffic and ELBs for HTTP traffic.

We could require that all hostnames be the same and change the cluster to bounce SSH traffic through the ELB to the HAProxy LBs and use new VPC ELBs, or put HAProxy in front, or whatever else. But this is probably more work for us than letting them differ.

There are also some possible arguments for using a different hostname for Conduit CLI SSH access (conduit.whatever.com) that has different DNS-based load balancing behavior than other SSH access.

I'm planning to support this in the arc experimental branch, although initial support won't be optimized. We can look at ControlPath and/or adding batching to the protocol layer to improve performance once it works.

I'm in the same situation. This would be a great addition.

What do you need on differential.querydiff? We could just give you a modern differential.diff.search with a revisionPHIDs constraint.

Performance concern. At least one use case requires us to scour *all diffs and all diff ids*. Also a desire to avoid having deprecated calls in our codebase.

(Is this a performance concern or do you just want like 6 fewer lines of code to maintain?)

Thank you, that was a very quick resolution, I just had the time to refresh the page !

The short answer is, maybe sure if we were funded with large sums of money and developer bandwidth, we'd have proper importers. We don't, we're not paid, and properly supporting an import pipeline is some ways away (years). Building your own script or off the script of yesteryear are how we currently expect people to build importers.

Please use Conpherence or Ponder if you have questions about Phabricator development and best practices.

(Also note that maniphest.edit is the preferred way to create and edit tasks in modern versions of Phabricator.)

There's no array_fuse() call anywhere near line 834 at HEAD of master, so I suspect this may already have been fixed in a more recent version.

I believe that using phid.query should be helpful.

I'm going to merge this into T11357. We can provide a "Delete File Data" transaction type when we implement a third-generation file.edit API.

This is working as intended, and not a bug. Administrators can not bypass policies. See the User Guide: Account Roles documentation: