These are so niche that I think we probably don't want to formally support them in the upstream.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 9 2020
Aug 2 2019
Aug 1 2019
Jul 12 2019
May 23 2019
Feb 5 2019
Jan 16 2019
Jan 14 2019
Jan 2 2019
Feb 5 2018
Feb 4 2018
Jan 26 2018
Jan 24 2018
I'm going to roll this up into T13047 since this stuff needs a rebuild in general.
Dec 21 2017
Oct 6 2017
I'm going to merge this into T4369, which has some similar discussion and more context.
Aug 10 2017
The community forum is a better place for this discussion. You may or may not receive help there, but we're no longer providing general Phabricator support here in the upstream (nor have we for a long time).
I'm having problems with script-and-regex too. I have asked in the community forum but without luck. I’m trying to add phpstan to the arc lint workflow, as explained in the documentation, but I’m unable to capture the error message. Here are my files:
Aug 6 2017
Jul 18 2017
Jul 9 2017
Jun 22 2017
No problem, without knowing how to reproduce an issue or see it locally, we can't really move forward here. Will close out and if it comes up again with another user and reproduction steps, we can re-visit. Thanks!
Sorry Chad,
See Contributing Bug Reports, specifically we need a full set of steps the upstream can reproduce to see the issue locally. I've installed Phabricator dozens of times on various platforms and never needed this command.
May 20 2017
For reference, even though this isn't right. I figured I'd put my notes here for someone else to find and help me out:
location / { client_max_body_size 32M; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Frame-Options DENY; proxy_set_header X-XSS-Protection "1; mode=block"; proxy_set_header Referrer-Policy no-referrer-when-downgrade;
@jefferai how did you overwrite the headers? I'm encountering this exact same issue.
May 12 2017
Hey guys,
Apr 12 2017
Apr 10 2017
Apr 9 2017
Apr 3 2017
Mar 26 2017
I'm just going to close this in favor of T12450.
Note there will finally be a little bit of documentation once this install rebuilds diviner docs: The url should be https://secure.phabricator.com/book/phabricator/article/cluster_search/ (eventually)
Mar 24 2017
Can you use a service like https://requestb.in with curl?
Mar 20 2017
Mar 19 2017
Mar 13 2017
(Presuming this is resolved since it's been open for a while without feedback.)
Feb 28 2017
I believe the semantics are consistent, but let me know if I'm misunderstanding or you're seeing something different:
Feb 17 2017
In the future (T550) we plan to allow arc commands to use an SSH key. I'm not sure if that will reduce or increase confusion.
It is somewhat confusing to have both an SSH key access level that allows repo cloning and an arc certificate level of access that enables different features.
Ah, yes -- this is where I got off track. In my head I had conflated being able to clone the repo with having the arc certificate installed. These steps are unrelated, I understand clearly now. As long as the SSH key is added in Phabricator and the Repo is activated in Diffusion, cloning it is no problem. In this case, I thought it was the lack of arc certificate blocking me, when in was actually just that I forgot to activate the repo. Whoops. Thanks for clarifying.
You should be able to can arc install-certificate --conduit-uri=https://whatever to install a certificate for an arbitrary install with no other configuration.
Fwiw, if someone else lands here (which I just did by Googling the same error message), the problem for me was the same as for the original poster -- having not first initialized a repo locally one way or another. My intuition (which is probably wrong) is that there is an interesting order of operations problem here.
Feb 15 2017
Jan 2 2017
Dec 23 2016
Dec 22 2016
Dec 13 2016
Dec 9 2016
I'm going to close this as resolved because we now have a setup check for it and haven't seen any more Apache version issues since this report (more than two years).
Dec 8 2016
Dec 7 2016
The intended target of the link is Cluster: Databases.
Nov 14 2016
A lot of arc help is version dependent, contextual, configuration-dependent, or extension-dependent, and this trend will only accelerate in the future. arc help is accurate; Googling for stuff will often get you help for a different version/configuration. Usage documentation is already available online.
Nov 8 2016
In T6653#167413, @maccath wrote:For reference and the benefit of people Googling how to configure a script and regex linter, here is a full example (using sass-lint):
.arcconfig file:
{ "linters": { // snip ... "sass": { "type": "script-and-regex", "include": "(\\.scss$)", "script-and-regex.script": "sh -c 'sass-lint -v \"$0\" || true'", "script-and-regex.regex": "(^((?P<file>.+): line (?P<line>[0-9]+), col (?P<col>[0-9]+), (?P<severity>[^\\-]*) - (?P<message>.*) \\((?P<name>[a-z\\-]+)\\))$)m" } }
Nov 6 2016
You should file a new bug report, describing exactly what you did and how we can reproduce the problem.
@epriestley where is the propper place then to help improving documentation?
To report a bug, please provide complete reproduction steps. We can't fix issues we can't reproduce. See Contributing Bug Reports for details.
Oct 9 2016
Oct 7 2016
Sep 19 2016
In case someone else ends up with my original problem, I'll mention that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/comments/69 fixed it.
Sep 15 2016
I hit this as well - I was able to fix the handful of tasks created before setting "search" -> "true" by just re-saving those tasks.
Sep 10 2016
Most of this stuff here no longer applies and there is now more NUX and other states available. In general I think we should try not to write documentation around UX issues.
Sep 7 2016
We also say "Only supports JIRA 6" but that means "JIRA 6 or newer", since JIRA 7 works fine.
Sorry for the late reply. What an incredibly well written and thoughtful response! Thanks!
Sep 1 2016
Aug 31 2016
Aug 30 2016
Thanks for the report. This should be fixed in HEAD of master, and fixed in production some time in the next 24 hours when the docs regenerate.