-
```
update libyuv used by chrome.
webrtc and gtp use the chrome version of libyuv now, so to update those
projects, chrome requires a roll.
It should be something like
cd d:\src\chrome\src
gclien…
-
This would prevent errors like: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20iOS%20Engine%20Release/12929/overview propagating post-merge.
-
Currently, the extension runs independent of the protocol, but it should only ever run on `https:` sites.
-
As of today, `et` has a very limited set of flags:
(Some flags omitted below for readability)
```sh
flutter % et help build
Usage: et build [arguments]
-h, --help …
-
Not sure if this has already been considered, but the addition of Chromedriver would be really helpful. Doesn't look like there's an easy way to get Chromedriver and its dependencies on my Chromebook
-
As I understand the worker configuration definition. a worker can have a combination of properties, such as this one in the dockers example:
```
platform: {
properties: [
…
-
The engine is a necessarily complicated product and can be difficult to work in for contributors that do not frequently live in the engine code. Personally I have to open a wiki page or two every time…
-
```
update libyuv used by chrome.
webrtc and gtp use the chrome version of libyuv now, so to update those
projects, chrome requires a roll.
It should be something like
cd d:\src\chrome\src
gclien…
-
```
update libyuv used by chrome.
webrtc and gtp use the chrome version of libyuv now, so to update those
projects, chrome requires a roll.
It should be something like
cd d:\src\chrome\src
gclien…
-
```
update libyuv used by chrome.
webrtc and gtp use the chrome version of libyuv now, so to update those
projects, chrome requires a roll.
It should be something like
cd d:\src\chrome\src
gclien…