commit | 43950f5636bf47b69a29d48508161b18e6a77c5f | [log] [tgz] |
---|---|---|
author | Jinseong Jeon <jsjeon@google.com> | Fri Apr 19 13:57:48 2024 -0700 |
committer | Jinseong Jeon <jsjeon@google.com> | Mon Apr 22 17:45:30 2024 +0000 |
tree | d27d38da3b327a3eb0e94131f141a451ac35b454 | |
parent | b7da9a81c2b0d450a57cfbc1e79f73d83d683c6f [diff] |
Eagerly dispose app env generated for the other KT UAST plugin Until we fully switch to K2 UAST, there is a chance that users' AGP modules run Lint with different KT UAST plugin, e.g., with manual opt-out per-module while global opt-in, or depending on language version (after b/333565234). At Ie6595f4a35ecc6b59bff7c3466ec9345ad4742c3, we cleared cached KT UAST plugin, but in AGP gradle daemon, the overall application environment can still exist, resulting in app-level service conflict. In this commit, UastEnvironment creation will check if there is such sticky app env that is created for the other KT UAST plugin, and if so, eagerly dispose it so that the newly created UastEnvironment will use the fresh app env. Aside from that, FE1.0 service registration is sealed with app lock. Bug: 323029887 Bug: 333731151 Bug: 333565234 Test: manual lint runs on MyApplication65 from ag/26948216 Test: bazel test \ //tools/base/lint/libs/lint-tests:tests.test \ $(bazel query 'kind("lint_test rule", //tools/...)') Change-Id: I62f984181fdaf46963b6c1c1fd88ba39198f1427
This project contains: