Merging in T8881 as its the same business problem here - a user blew through this dialog and we can do a slightly better job forcing them to read things.

I seem to reproduce this when I try to load the revision specified. I assume mentioning it does bad things. :D

We haven't seen any more reports of this and can't reproduce it ourselves. Ergo, I think its something strange with your configuration, or perhaps some localized supernatural activity. Sorry we can't be more helpful, and please do re-open this is you have new insight as to software defect(s) we can fix here.

This is great. When / ever do you plan to be able to survive the whole AWS datacenter going out/

This is shipped from the user perspective and I didn't leave much crud around, but I hope to reduce said crud to 0 so leaving open for now.

I think Diviner is meant for these scenarios. Basically because

If you visit one of the commit pages, do you see the 'somebody accept a commit' message duplicated / other duplicated activity?

I think fixing this is basically removing the unique constraint on the "slugs" table in Phriction, and then using application logic to make sure that there can be only one active page with a given slug at any time.

I can't seem to reproduce this. See this test page here...

Hey @tiguchi - thanks for the report. I think it should be fixed if you update to HEAD. If things still don't work for you please let me know and I'll take another look. Thanks again for the report!

Is there any actual review happening in this workflow or is it just about getting the 100+ audits to an accepted state as quickly as possible?

How come the user shouldn't comment? What is the business value of letting someone read this information, but not interact with it further?

...we're really looking for as much information as you can possibly provide about what you're trying to do here. As a simply stated feature, the answer is "wontfix".

Please do re-open this if / when you have time to answer @epriestley's questions. Also, check out

Let us know if you weren't able to resolve this following @epriestley's instructions. Assuming things worked out for now... Thanks!

See T3105#31820 for the reasoning for the "wontfix" status, which remains true today.

Let us know if restarting didn't resolve this. Thanks!

Can you provide more examples of feed stories that you'd like to delete? Generally, I think the goal we want to solve is to make feed useful such that you don't feel the need to X out stories, so more context on what you want to remove is very helpful. In the example given, I would think we might want to aggregate those stories and just show a single one.

I think this problem is with Azure, your configuration with Azure, etc, since if it was a generic issue serving files we'd be hearing more about it.

In T4214#120383, @qgil wrote:

What I didn't explain is that this Phabricator header was one of the most contentious topics among some of our most experienced volunteers and some of my managers too. They were happy to fork the header and assume the cost of maintaining the local code. I calmed the discussion by promising that one day this will be fixed. So yes, communities care about their logos.

PS: if my story encouraged you to lower the priority from Normal to Wishlist, maybe I should have done something different on my Friday afternoon. :)
PS2: The "spooky eye" is not an hypothetical expression, I'm just quoting. In any case, as of today it doesn't compete with the popularity of the "Phabricator" wordmark.

In T4214#120376, @qgil wrote:

We call it "Wikimedia Phabricator" and our community talks about "Phabricator". Therefore [Wikimedia logo] + "Phabricator" makes sense, while "[What is this spooky eye?] + "Wikimedia" will create more confusion than the vanilla Phabricator header. I think the perceptions in other communities using Phabricator will be similar. All of them know their own logos, and all of them will recognize "Phabricator".

I think that Phabricator should be "white label" software that anyone can take and quickly configure so it looks like it comes 100% from their own organization. That way, new users won't have any idea they are using Phabricator, and will instead think their own organization has some sweet tools, or in the SaaS competitor case, that SaaS competitor A really builds some great software!

See T8516 for the "detect misconfiguration better" task.

In T8453#120118, @tao_qiping wrote:

Sorry I raised T8436, as this ticket is focus on search custom field. so I re-open it again as I still can re-repro it on list field, below is my custom field. can u please verify a list field to see if it is fixed, if so I may need to update my code to latest.

"tke:system": { 
     "name": "System", 
      "required": true, 
      "type": "select", 
      "search": true, 
      "copy": true, 
      "options": [ "", "SharePoint", "Agent Appointment", "Agent Registration", "AR Overdue", "Business Travel Approval", "CAPA (Corrective Instruction)", "Cash Advance Approval"]
      }

Can you take a step back and explain a bit more how you and your team is using Conpherence? Basically, I'm trying to understand how come there are so many active threads at once for an individual and what the nature of these threads is...?

This is just a regression caused by D13058.

But how will you get SEV0 bugs if you don't dabble in infinite recursion?

Oh whoops, I guess I took awhile to submit that comment and missed the update notification. :/

That is an example URI and would be different for your Phabricator installation. For example, for this installation, https://phabricator.example.com/oauthserver/client/create/ is https://secure.phabricator.com/oauthserver/client/create/

Just filed T8488 which may make this better.

Submitted that a bit early. Basically I think the distinction here is adding some confusion. Very very open for discussion. :D

See also T7589, which for the durable column plans to improve the recent room / messages switcher.

This is again by design. @chad - please note this task.

That sounds fine to me, but I think I iterated to @chad's dream state... I actually think we used to have "(No Title)" or something for a time...