If diffusion.search existed, you could call it with repository.phid to pull the short name, callsign, ID, etc. Would this be sufficient?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 7 2016
Also known as the far more hilarious CURLE_OPERATION_TIMEOUTED.
This may be cURL 28, CURLE_OPERATION_TIMEDOUT. We have a 60-second timeout on this build step. Is it possible your server requires more than 60s to acknowledge the initial request?
That is, it already supports subscribers, the field just never got built in the UI.
We probably will build this sooner or later since it's free when Countdown eventually swaps to EditEngine.
Sounds good. I'm going to close this out since we don't plan to pursue the particular rule it describes and I think other related work is already covered elsewhere.
After D15427, this should be pretty clear for "Land Revision".
Importing SVN repositories as single repositories is recommended (Facebook's had several million commits in 2011, IIRC).
This hasn't happened again and I think it's less reasonable to expect it to work in modern Phabricator.
I think this was resolved at some point -- this is the behavior at HEAD, which seems broadly reasonable:
See also T2225 for a concrete issue caused by showing enormous numbers of paths (unbearably slow page loads because of the raw wire filesize).
This was fixed a couple of years ago in D4730, and works fine on the modern LLVM install: http://reviews.llvm.org/rL170845
After D15424, arc fails when failing to push the staging area.
I've marked D15424 as fixing this, although I don't have a detailed understanding of exactly what goes on in the git protocol and which heuristics it is using. In particular, I haven't been able to trick it into doing too much work locally (maybe it also looks at parents?).
This is on a daily cron, I think you missed the update by a couple of hours. Link works OK for me now.
Hi! How can we reproduce this behavior?
Please describe the root problem you're facing when requesting features. See Contributing Feature Requests and Describing Root Problems for details.
Mar 6 2016
Mar 5 2016
Thanks for the report! This was a bug.
I believe this wouldn't solve your problem: I could add two files, A.c and B.c, and add a header to only one. This would pass the rule but fail what you intend to enforce, I think.
oh, you also have to put an interface on the device in order to bind it
Create any device, create any service, bind the service to the device, then click "Details":
Drydock and Almanac are now available in the cluster. Here's a rough guide to configuring them -- I'll turn this into something formal once things work a little more smoothly.
Yeah, that claim assumes someone will arc diff some published commit sooner or later (i.e., run arc diff while on master with no local changes). While this wouldn't happen on a normal workflow or on purpose, I suspect it happens more-often-than-never.
Mar 4 2016
I think that'll fix it. Thanks for the report!
I can't recall any reports of those issues on other installs, and we haven't experienced them ourselves. I don't think these issues are typical, frequent, or widespread.
Quick update here ahead of deployment tomorrow:
What are the specific things you want this feature for? Please describe the root problem you're facing. See Describing Root Problems for help.
Mar 3 2016
Given how frequently ANSI characters and similar occur in build logs, this probably doesn't make sense until after we have support for binary data on the API (T5955).
Upstream builds have been in production for some time. There's always more work to be done, but I don't think there's anything actionable left here that isn't covered elswhere.
Is the outcome of this task likely to be select a source for a given project where source might be manual, or ldap, or something custom?
I don't intend to change that limit. I believe there is very little value in reviewing 1000+ file changes from the web UI, and that the 1K file limit is a reasonable one.
That commit is changing more than 1,000 files.
In T8612#163197, @paladox wrote:What about per file diff viewing it would hide them by default but add an option to each file that says show diff.
Yes, this should eliminate the need to sync/cron/do anything.