7 Commits

Author	SHA1	Message	Date
Dan Miller	d2cc5c3708	Merge branch 'master' into Version-v10.6.0	2021-11-16 01:08:06 -03:30
Dan Miller	381d1fe7a9	Run yarn lavamoat:auto	2021-11-11 16:25:47 -03:30
Dan J Miller	82a95864f7	Support for Layer 2 networks with transaction fees on both layers (#12658) ... * Support for Layer 2 networks with transaction fees on both layers * Use variable name in transaction-breakdown * Add comment on code source to ui/helpers/utils/optimism/fetchEstimatedL1Fee.js * Fix unit tests * Ensure values passed to are defined * Fix activity log	2021-11-11 14:06:33 -03:30
Dan Miller	22468ffdb1	Run lavamoat:auto	2021-11-09 17:32:31 -03:30
Elliot Winkler	e951fe6a64	Improve autorebuilding in dev to reduce CPU load (#11886) ... On an M1 Mac, when running `yarn start`, CPU can spike to 100% CPU, and sometimes a bunch of `mdworker` instances will get spawned. This seems to be caused by the file-watching mechanism used in dev to automatically regenerate the build when something is changed. More specifically, we are using an older version of `watchify`, which uses an older version of `chokidar`, which is the package that actually does the watching. v4.0.0 of `watchify` upgrades `chokidar` to v3.x ([1]), which comes with "massive CPU & RAM consumption improvements" ([2]). After the upgrade, CPU usage decreases to 20-40%. [1]: https://github.com/browserify/watchify/blob/master/CHANGELOG.md#400 [2]: https://github.com/paulmillr/chokidar/releases/tag/3.0.0	2021-10-25 13:56:26 -06:00
ryanml	078ba89ebd	Run yarn lavamoat:auto	2021-10-19 15:52:06 -07:00
kumavis	cb174ff8e6	Lavamoat build system integration for WebApp (#12242) ... * lavamoat - add lavamoat to webapp background * test:e2e - add delay to resolve failure * test:e2e - add delay to resolve failure * build - add a switch for applying lavamoat, currently off for all * test/e2e - remove delays added for lavamoat * Revert "test/e2e - remove delays added for lavamoat" This reverts commit 79c3479f15c072ed362ba1d4f1af41ea11a17d63.	2021-10-05 12:06:31 -10:00