(Or we should just remove CAN_JOIN -- is there any actual use case for read-only rooms? If there is, shouldn't users still be able to join those rooms in order to follow them, just not send messages?)

A related issue is that CAN_EDIT does not imply CAN_JOIN, so users with CAN_EDIT but no CAN_JOIN can get a policy error while trying to join.

+1 for random grepping. Thanks for the fix!

(Your diagnosis of the root cause was also correct.)

I deployed D17346 and rebuilt the indexes on this install with bin/search index --type DivinerLiveSymbol and behavior now seems correct. Thanks for the report!

Please file a new task following the instructions in Contributing Bug Reports if you'd like us to take a look. We need all that information before we can start looking at a bug.

I'm going to merge this into T12196; this is almost certainly an issue with PHP7. Upgrading to PHP 7.1.2 may resolve it.

When accessing an ICS export of all events I can see (https://secure.phabricator.com/calendar/export/3/):

Unhandled Exception ("Exception")	
DateTime::__construct(): Failed to parse time string (@) at position 0 (@): Unexpected character

@chad - How can I be involved with any progress on this front then since now it is planned?

See T11429

Do you think there are any intentions to fix this issue for windows users? At least in far future?
Me and my colleges are still working with an old arcanist version 737f5c0d. If this workaround breaks, there would be no way for windows users to work with arcanist. Except using a fork containing D15675.

I think this compression had messed up with HTTP served Git repository. Git complains with

I presume there is no logical need to add the same panel twice to a dashboard.

Seems functional.

Possible followups from D17344:

Here is an example of a report that is satisfying several use cases from the comment above, https://secure.phabricator.com/T10339#159098. Those use cases, fleshed out a bit, include:

More use cases:

This now just says "Login" in text.

Hard to say since it fell off the roadmap a year ago, but we do have rough plans to ship Nuance (pre-requisite) in the shorter term.

See Planning for help with timelines and status.

Where does this feature stand? I wasn't able to find any documentation on how to use this, but it also looks that a non-trivial amount of work has been completed towards this goal. Is this something still in the immediate roadmap? Being able to easily integrate GitHub issues into Phabricator (and back) is a big roadblock to adoption for us.

See downstream for general discussion. See T12256 / T12257 for upstream followups.

Example: I disabled a bogus user when the "confirm your e-mail" MTA job was on its ~200th attempt. It's now at its ~240th attempt :)

Ah, thanks! Good to know what my own community is doing.

This is a copy of downstream https://phabricator.kde.org/T5242. See that task for discussion.

Can we please add the keyword subscribe or subscribers in this task title? I looked through 2 pages of subscribers search before filing a dup. I know now I was searching the wrong term, mention would have given it to me instead. But they are related.

We would also like this behaviour, and currently use a workaround to accomplish it (which is why we never came here looking for a fix). We created a custom Create Task form that sets the default view policy to include subscribers.

Thanks, this should now be fixed in HEAD of master. Let us know if you run into anything else.

Hi Evan,

Resolved by D17337.

The WMF downstream has some similar discussion here and in linked tasks: