I’m confused. Will what it parses depend on the languages installed/available and setup on the server?
I would expect the patch parser to recognize patch files of any language, without depending on runtime environment languages.

tested with both applied and still fails with LC_ALL=fr_FR.UTF8

@bapt, @ite-klass - could someone please test D9922 + D9938? We have tons of trouble testing this stuff since we run all english otherwise.

Other installs should NOT run bin/storage adjust yet: we have some things that still need cleanup.

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

Just wanted to say I am having the same issue on an existing Phabricator install.

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

While I remember:

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.

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 has widespread impact, notably preventing import of repositories with an emoji anywhere in them with no workaround.
High Support Impact Massive data migrations.