It's important for us to understand the why of a feature request, since we won't likely add them for hypotheticals. See Describing Root Problems for how we look to describe problems.

(And there are no configuration settings you can change which will possibly impact or resolve it -- it can only be resolved by an upstream fix to the problematic implementation.)

@epriestley
Yes your point about security risk is completely valid. Just wondering if there is something that can be done whilst avoiding comprising security. Perhaps a console command to unlock all objects owned by a specific user, changing all custom policy objects containing the user and adding administrator access.

Sorry, I wasn't very clear -- I know exactly why this is happening. It isn't related to configuration or arcanist (it's an implementation issue related to D14970), so I don't need any more information.

Quicksand issue most likely. Thanks for the report. I was mostly curious is people are using the column in the real world.

Yeah, these are "common" controls, but I think they only get used in Herald?

oops~

Hi chad,
We ran into this bug because a colleague use it and couldn't display project tasks.

Closing since this isn't a bug report. See Contributing Bug Reports for what we look for in a bug report (specifically, repeatable steps by us to reproduce the issue). General questions on using Phabricator are better suited for Ponder. Thanks!

Can I ask if you actually use the Conpherence sidebar? Or is this just something you ran across testing?

Uploading a file to Maniphest tasks sets the permissions to the view policy of that task. If you need to just upload any file to Phabricator, just drag and drop it onto your homepage or use the Files application.

If they can post to the blog, they can read the draft.

I've been trying Phame out internally and it's pretty sweet. The one thing I could not figure out how to do (and maybe the answer is I can't) was how to share a draft with someone to read before it's published. I tried adding them as a subscriber to the draft but that did not give them permission.

Daemons now do both reads and writes, and may need to do reads and writes which are nonlocal in cluster configurations. So I think the pathway forward here must be to expose local disk storage over HTTP with S3-like raw APIs (read, write, delete).

Sounds good.

Ok, as far as I'm concerned I'm happy with what P1895 provides and this task can be closed. The more elegant solution seems to be part of T9530, making this task entirely superfluous.

Here are some more details about the error:

I increased upload_max_filesize in the vhost to 1G. Afterwards the arc land itself worked but the commit done by phd still shows the descibed log entry.

In the buildable page that lists all the builds, I was experiencing 6 second load times until I added:

Page loads in Harbormaster for us are almost instant after adding this index.

@sgrimm In your large post, you have a link that says 'Add a Herald Rule'. This link appears to be intended as a template so you can replace the domain with your own domain.However, clicking it actually brings you to the working domain http://phabricator.xxx.com. The result is funny and unexpected, but likely not intended. Maybe it should be changed to phabricator.example.com to prevent people from being linked to porn :)

jet fuel can't melt steel beams.

I didn't add to Herald as I wasn't sure whether it's specific to these forms or if there are other forms which have these components and the same problem.

In T10187#154936, @chad wrote:

• Other projects are coming to workboards

Nah, it's fun seeing software have some personality. I guess that what I wanted to say was that this one stands out noticeably against all of the "Save," "Cancel," "Execute Query," and other buttons, not that it's a bad thing.

You can always turn them off with phabricator.serious-business. :)

@chad Come to think of it, of course, you're right. This one just stood out, somehow, maybe because it's so much more visible. Maybe it's because everywhere else they are nouns but here it's a verb which is kind of unusual?

Many of the concepts in Phabricator are Nautical by Nature. Maniphest, Harbormaster, Drydock, etc. It's not much a pirate thing, and oddly is not related to me previously being enlisted in the Navy (since @epriestley picks the names).

My 2¢: "Set Sail for Adventure" made me check if I hadn't somehow switched to the pirate translation. Silly UI is ok with me but maybe less nautical, to not steal the pirate translation's thunder when it's turned on a few times a year?

• Other projects are coming to workboards
• Hovercards are being redesigned, adding "subtask of" or "blocks" info would be feasible

This is an issue in the implementation, not a configuration issue.

It'd be good to know if this resolves your issue, since our error message is debatable on "useful".

upload_max_filesize: Maximum file size PHP will accept in a raw file upload. This is not normally used when uploading files via drag-and-drop, but affects some other kinds of file uploads. If you exceed this, Phabricator will give you a useful error. This often defaults to 2M. Set this to at least 32MB.

Another use case for this query would be to visualize the 'status' of subtasks on a workboard by filtering on 'blocked by Txxx'. For example, maybe some of the subtasks are Done while others are languishing in Backlog.

To the best of my current knowledge, there are no actual problems with the Node server (empirically, it is easy to install and maintain, stable, and works well) and no viable pure PHP alternatives anyway, so I have currently have no plans to ever pursue this. See above for a description of the type of new information which could affect these plans.

This has been open for about 18 months without anyone coming up with any really concrete use cases to motivate any of these flags, so I'm just going to close it out until such a motivation develops and this becomes non-hypothetical. I haven't seen any misuse here personally in the upstream, and we haven't heard too much feedback about this particularly, as opposed to some general difficulty finding the right projects in typeaheads, particularly for newer users.

These now show hovercards, which will show project information after M1455 is implemented. I'm just going to close this in favor of T10054, which is an umbrella task tracking related work.

These seem alright, I haven't been bothered by them.

I don't have any current plans to pursue this, per se, in the upstream.

You can now customize "Create" forms and prefill (and, optionally, lock) their policies. See:

I don't plan to support this. I think "files attached to any object tagged with this project" is not likely to be a useful view in most situations, and haven't seen other requests for this. We inched into this territory with a "files" module in Conpherence some time ago and it was felt pretty much useless in practice.

As a workaround, you may be able to use the API (maniphest.edit) to, e.g., have a bot or script post comments to tasks.

I think this feature is far too niche (use of git describe is rare in the wild) and crude (it doesn't actually tell you information about deployment status, and you don't actually use the raw git describe output, and the output is not necessarily related to the build) to bring upstream. We also already link up the commit, which shows branches, which usually provide some related information in standard setups.

If disabling a user removed all policy controls, an attacker who compromised an administrative account (or a malicious administrator) could disable other users and then access information they could not otherwise see.

Whilst this is one method it isn't useful for administrators without route access. It seems to be an unnecessarily long-winded method having to unlock each item one by one.

See also T9853, which includes an extension to do this.

I'll have a look at T9853 (sorry, didn't find that, when I searched... might have had "open" set), it looks close to what I had in mind at a first glance.

I have the same issue with SVN+SSH, but not with GIT+SSH. I used strace. This is the part where it breaks - looks like it breaks after the chdir call (in the middle of the snippet):

The most recent ruleset seems to be working pretty well for me. It hasn't been spazzing out and popping up all over the place, but has been there the couple of times I actually wanted it.