Maybe not enough but depends from your point of view...maybe the real solution is give the opportunity to ask if you want gravitar or not.

In T6261#78754, @leonardo.furio wrote:

Perfect!!! thank you!

Perfect!!! thank you!

D10651 will at least prevent future issues, will have to follow up if a migration is possible.

Alternative fix is to delete Gravatar support.

Usually this is because outbound HTTP requests are firewalled and we're trying to fetch a Gravatar. Workaround is to disable security.allow-outbound-http. Real fix is to time out the request and/or detect this during config.

No worries, I am very confident, and if someone hits it they'll report it. Thanks!

Sorry, I've been having other phabricator fires today. And I changed my config to no longer import production.conf, so it's a bit hard for me to test it -- sorry!

Also, probably should be in a separate task, but the ability to outright delete a column/list would be useful, especially since active tasks can exist in hidden columns which is very confusing.

also, if we can get a procedure for removing 'backlog' lists created due to this bug, it'd be a real help. I have one board that currently has eight backlog columns :(

Support Impact This breaks boards in a confusing/surprising way and @tcook hit it in the wild (but I don't think developed repro steps).

well, actually I landed it so just update to HEAD and let me know if I didn't fix it. =D

Closed by commit rP69b1ff303238.

@csilvers - can you test D10643 if you have a second?

Closed by commit rP928b4edffb66.

Support Impact This breaks older installs which used phabricator_read_config_file(...) with any of the default config files when they attempt to upgrade.

I believe using %T instead of %Q probably fixes this.

Is the proposed fix correct? (Binary just needs to be quoted? ...and that will still work in newer sql?) I'd implement it slightly differently with the wonders of qsprintf

(This doesn't technically get harder to fix over time.)

Support Impact storage upgrade is broken on old MySQL and installs attempting to upgrade will be left in a nonworking state.

• Databases also create with the wrong collation for old MySQL.

Support Impact We interact with this option badly, in a way that prevents installation or breaks installs with no clear path forward.

Projects are the privacy setting. You make a Project, set the members and who can join, then lock down other areas of Phabricator with that Project.

I read all this thread and still cannot figure out if I can apply any policy or privacy setting for a project. It is a real trouble. Projects need documentation. But not everyone should access this project.
How does Phabricator approach this issue?

While I remember:

In general, a user who can view a task can already take a screenshot of it and share it with whoever they want. I think of this as very similar to that, except that there's an audit log and the grant is revocable.

I'm going to disagree here with the utmost respect.

Support Impact Inconsistent and confusing.

Support Impact This is inconsistent.

Support Impact Addresses various support issues with multiple occurrences.

Support Impact Broken with no workaround on a nontrivial subset of diffs.

Support Impact This is just completely broken and possibly destroys or mangles data.

Support Impact The remaining stuff is pretty hard to use.

Support Impact The current behavior is unexpected and confusing.

Support Impact This creates various confusing application inconsistencies.

Support Impact This is just support impact from HackerOne researchers each reporting this issue. We should resolve it before SAAS.

Support Impact Inconsistent and confusing, although mostly fixed now.

Support Impact Disruptive in the wild and unscalable.

Support Impact This is fairly broken, although there isn't a clear fix for it.

Support Impact Substantial effect and unclear next steps.

Support Impact Technical debt and inconsistency.

Support Impact This has cropped up a number of times and is surprising and broken.

Support Impact This is broken.

Support Impact This is confusing.

Support Impact While this is mostly resolved, it created inconsistencies and blocked other tasks.

Support Impact This is generally a support-focused feature.

Support Impact This is broken.

Support Impact APC/OpCache have a dramatic impact on performance but are not straightforward to configure correctly.

Support Impact Significantly affects non-English users. Many workflows fail when we look for English text in command output.
High Support Impact We're likely to get more of them over time.

Support Impact The transition to .arclint seems to have reduced the lint-related support burden substantially.

Support Impact Support cost for the in-the-wild instance of this was seriously more than an hour.

Support Impact This doesn't really create much of a support burden but is confusing and stupid.

Support Impact This feature is fairly useless right now for all but the simplest things.

In T1191#78120, @epriestley wrote:

Support Impact This has widespread impact, notably preventing import of repositories with an emoji anywhere in them with no workaround.

Support Impact A lot of application functionality is not accessible over Conduit (or is accessible only in a confusing or broken way).
High Support Impact Removing methods gets harder over time, and this broadly limits our ability to expand many Conduit capabilities.

Support Impact Conduit can not represent some messages (e.g., diffs with non-utf8 text), which has no workaround, and is very difficult to use relative to other APIs.
High Support Impact Waiting on this makes it harder to deprecate the old stuff (since it will be more widely deployed) and may mean we need to convert or modernize more methods.

Support Impact This is wildly difficult to diagnose because it manifests as a mysterious hang.

Support Impact This is confusing.

Support Impact This is inconsistent, confusing and broken.

Support Impact Almost all users doing code review are exposed to these workflows and we have room to significantly improve them.

Support Impact This has widespread impact, notably preventing import of repositories with an emoji anywhere in them with no workaround.
High Support Impact Massive data migrations.

Support Impact This is broken with no real workaround.

Support Impact This is confusing and trivial.

Support Impact This is broken.

Support Impact These behaviors are confusing and make it difficult for users to find the useful text in the output.

Support Impact This completely breaks the interface.

Support Impact This behavior is confusing.

Support Impact This behavior is surprising and buggy.