Our current top crasher is an unclear error when ProcessManager fails to resolve an executable path. To fix this, we'd like to being adjusting the process resolution logic and adding more instrumentation to track failures. In order to begin the process, the ProcessManager has been folded back into the flutter tool
* ➕ Added a new template for [NumberFo
rmat] with positional parameter(s)
* 🔨 Renamed [numberFormatTemplate] to [numberFormatNamedTemplate]
* [gen-l10n] Fixed generation error for namedParameters and optionalParameters
* [gen-l10n] Fixed string value generation for optional parameter
* [gen-l10n-test] Added new tests for `decimalPattern`, `percentPattern`, `scientificPattern` and formats with optional parameters.
* 🔨 Removed trailing whitespaces
* 🔨 replaced [_generateStringParameterValue] with [generateString]
* 🔨 Specified variable types in NumberFormat templates.
* ➕ Added a new template for [NumberFo
rmat] with positional parameter(s)
* 🔨 Renamed [numberFormatTemplate] to [numberFormatNamedTemplate]
* [gen-l10n] Fixed generation error for namedParameters and optionalParameters
* [gen-l10n] Fixed string value generation for optional parameter
* [gen-l10n-test] Added new tests for `decimalPattern`, `percentPattern`, `scientificPattern` and formats with optional parameters.
* 🔨 Removed trailing whitespaces
* 🔨 replaced [_generateStringParameterValue] with [generateString]
* 🔨 Specified variable types in NumberFormat templates.
* [gen-l10n] ✅ added test for parameter having special characters in string value.
* Accidental tab added to integration test
Co-authored-by: arish <arishsultan104@gmail.com>
= gets escaped into %3D which seems to be tripping up cmake on windows since % is a control character. Switch to base64 encoding, since this does not have % nor , in the output character set.
This change is not trivially cherry pickable, and isn't tested on windows aside from my local, manual tests due to the planned CI work not being complete yet.
Fixes#75017Fixes#74705
This stops them attempting to own a D-Bus name, which may not be possible if the
app is sandboxed (e.g. in a Snap). It's also probably what most developers would
expect is the correct behaviour by default.
