| commit | 24575c2fde2790676f081154105180f8946abe8d | [log] [tgz] |
|---|---|---|
| author | Solly Ross <sollyross@google.com> | Fri Sep 30 21:29:08 2022 +0000 |
| committer | Solly Ross <sollyross@google.com> | Fri Sep 30 21:29:08 2022 +0000 |
| tree | 3dcd515a968a874f508d8e983f479cf23887a42f | |
| parent | b0f0ad5f30c9911ed65151a509d0576881159265 [diff] |
[infra] fix race in flags plugin (no longer plugin) There was an inherent race in the design of the flags plugin, in that it was writing package.json, meaning if it started writing before another build read package.json, the other build could read an empty file (due to how file writing/truncation works). This means that flags won't be updating during watch, but that could be solved in a follow-up CL with a manual watch impl for it, or maaaybe by turning back into a plugin & doing one of the atomic file write strategies (write, then move, for example), but this seems like more work than it's worth atm. Change-Id: Id15c20fc3e35ec1ae409c0b786eae7f5a966e188 Reviewed-on: https://fuchsia-review.googlesource.com/c/vscode-plugins/+/731343 Reviewed-by: Miguel Flores <miguelfrde@google.com> Kokoro: Kokoro <noreply+kokoro@google.com>
This VS Code extension implements the commonly needed functionality for Fuchsia development.
This is a Work In Progress Currently supporting:
The FFX tool path can be set under Settings > Extensions > Fuchsia SDK. If this path is not set, the extension will automatically search for it at:
Use of the Fuchsia core developer tools is subject to the Google Terms of Service. The Google Privacy Policy describes how data is handled in your use of this service.