See T12298#213181.

@epriestley Yep - like what you're doing there :)

So I don't forget:

Maybe the "Install Arcanist" header on Quick Start could be like:

Oh, no, it's just to do with the ordering of the links vs the annotations: if you're totally new to phabricator, you're going to get tripped on the "quick start" link which says "install stuff" and in the middle links you back two pages...

I'm assuming he wants us to duplicate the installation information onto Win/Mac pages or only link to those pages after installing arcanist.

That is, this passage:

There's a short version and a long version. Each version links to the other version, saying "here's a different version of these instructions, if you'd prefer that one". How could we make this more clear?

Thanks! I guess nobody ever noticed that before!

@pouyana Here's a workaround for you. In your notification.servers Phabricator configuration, add path: "/ws/" to the client server. Then, modify your apache configuration like so:

Thanks for the report! This should be fixed in HEAD of master, and promote to stable tomorrow, a little more than 24 hours from now. Let us know if you run into any issues.

Thanks for the report! This should be fixed in HEAD of master, and promote to stable tomorrow, a little more than 24 hours from now. Let us know if you run into any issues.

Yeah, I'm basically just keeping this open as a dumping ground for the moment and purely selfishly because my segfaults aren't resolved yet -- brew didn't have PHP 7.1.2 last I checked, although it seems like it now does. I've upgraded and I'll see if that improves things.

Ooh just kidding. ⌃+Refresh fixed everything

We require all bug reports provide complete reproduction steps. The main reason is so that anyone can follow and reproduce the bug in a local environment. Skipping details makes it difficult for most (or anyone but @epriestley) people to provide you with help.

Hi @rsmarples, unfortunately I don't know how to reproduce this based on your steps provided. Specifically, I do not see a broken "reference" link in the details of the commit. Do you know what additional steps I can take to see this bug locally? Everything looks formatted fine?

In my scenario the external companies would not see eachother's tasks (separate Spaces), nor other internal items (default Space). However the developers within my company would need to see things from across multiple Spaces.

Yeah, but I still want Spaces to be "hard walls" around content. If it's just some minor dashboard permissions, it might be overkill (ie, they both need to see same tasks).

Do these dashboards contain sensitive information?

For the use-case I was trying to outline in T9501, this would be the case. We work with a handful of external companies and use Phabricator for organizing and communicating work. We also use Phabricator for our code review. Each project with external company (People, Projects, Maniphest) is organized into separate Spaces so that they are fully isolated, and we have a default space for internal use for Diffusion/Differential. Ideally when a user from Company A logs in they would land on a dashboard that shows only the Projects/Maniphest for them, while Company B user logs in and only shows the Projects/Maniphest for them.

In T12308#212972, @chad wrote:

Do these dashboards contain sensitive information?

Basically we're in feature request territory, and we'll want to understand the root problem installing all these dashboards solves before deciding on what to build.

Do these dashboards contain sensitive information?

In T12308#212968, @chad wrote:

What is your expectation here that we do?

I think this is still the best way we have to let you if the dashboard visibility is over-restrictive or mis-installed. I'm not sure magically disappearing it solves anything. It might help to know more about what you are trying to do (was this on purpose, or a mistake) in order to try to better inform admins when they order dashboards like this.

What is your expectation here that we do?

Probably very similar or even dupe of T9501

It is expected that taskmasters will exit and restart after an unexpected failure, but this should not trigger setup warnings. I'll see if I can reproduce this.

This might be the same as T12302, but I'll see what's going on.

Persistent chat was originally a separate column (so it didn't overlap with anything on the page) but was brought into the main page recently.

Just as a side note: PHP 7.1.2 was released like a week ago, and I have not seen any more spurious segfaults on my instances when doing imports or anything like that on the server. The arc liberate bug remains dead and I have not seen any more faults in arc either. Builds should now be available in most PHP 7.1 repositories (in multiple distros/systems), so I suggest an upgrade for anyone who's affected.

Yeah I'll take it, pretty sure it's my fault.

Yeah I was planning on bisecting, but sounds like you're claiming this?

I think this is probbbbbbbably an actual bug unless I'm totally out of it -- possibly my fault from D17372.

I could be wrong

Also, note that in this install, Create Form links to /transactions/editengine/maniphest.task/edit/nocreate/, not to /transactions/editengine/transactions.editengine.config/edit/nocreate/. So, to the correct place, but "forbidden" one.
And there is simply no any other button to push.

This also seems related: https://secure.phabricator.com/D17262

Yep. How do I create the form I need then?

This isn't a bug, but is confusing.

Removed apache settings:

<LocationMatch "\.(?i:os)$">
    ForceType application/octet-stream
    Header set Content-Disposition attachment
</LocationMatch>

I don't believe we've seen this pop up again. I can't be certain because right now all the log files are empty, but that means the errors went away?

I'm just going to merge this into T12115, which isn't really related, but will rewrite this code and probably "fix" this, since a reproduction case seems elusive.

We were never able to reproduce this convincingly and as far as we know the reporting install no longer uses Phabricator, so I'm going to close this out.

1. Install Phabricator at the version noted above.
2. Import a GIT repository via observing a URI.
3. Note the reference HEAD -> master link broken on latest commit.

Please provide reproduction steps, we don't accept bug reports that ask us to go look at their server.

I believe we only get it wrong in the very specific case where you're attending a "Busy" event and an "Away" event at the same time. We'll show the dot color for whichever event started first, so if the "Busy" event started before the "Away" event you get an orange dot instead of a red dot (if the "Away" event started first, we show a red dot, but that's the right color to show).

rare

Maybe my calendar setup isn't common but I usually have multiple overlapping meetings each week - I know others at the same company manage their calendar in a similar fashion.

Some more shenanigans:

See also T12079 and T12219, although I'm not sure if either of those are duplicates of this.

Here's the note in PhabricatorPeopleQuery about this:

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.