[pull] main from bazelbuild:master #450
Open
+96,502
−35,098
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
…opying sandbox inputs/outputs. Also wrap it in an EnvironmentalExecException, as it seems more appropriate than a UserExecException; introduce separate failure codes while at it. (We should probably rethink whether SpawnRunner#exec should even be allowed to return a naked IOException, but that's a much larger change.) Fixes #23283. (cherry picked from commit 6ef9672)
(cherry picked from commit 26621d5)
(cherry picked from commit d243db6)
…mote_use_new_exit_code_for_lost_inputs` [ (cherry picked from commit 5ea0680)
…/`AspectComplete` events in BEP using new flag. Some services that consume large BEP streams need to be able to eagerly identify critical output files without keeping the entire BEP stream in-memory. Traditionally, these were reported in the `TargetComplete.important_outputs` field, which is deprecated because it can grow without bound without any mechanism to break up the set of files included in that field. The replacement for `TargetComplete.important_outputs` is the recursive `NamedSetOfFiles` representation which can be broken up arbitrarily and supports efficient serialization directly from `NestedSet` objects inside the build tool. Unfortunately consumers must keep the entire BEP stream in-memory in order to efficiently identify critical files when they are linked from a `TargetComplete.output_groups.file_sets` field. As a compromise, this change introduces a new field: `OutputGroup.inline_files`. By using a new flag, `--experimental_build_event_output_group_mode`, users can request that specific output groups report their files inline instead of using the recursive `NamedSetOfFiles`. This still suffers from the same failure mode as `TargetComplete.important_outputs` - a single huge output group can produce an extremely large single event. Unlike `TargetComplete.important_outputs`, users may restructure their build rules using additional output groups to shrink the size of their events. RELNOTES: A new experimental flag, `--experimental_build_event_output_group_mode`, allows users to change how a given output group's files are reported in BEP. The current behavior is `FILESET` which populates `OutputGroup.file_sets`. Users may now specify `INLINE` to instead report files directly in the `TargetComplete`/`AspectComplete` event under `OutputGroup.inline_files`. Users may also specify `BOTH` to populate `OutputGroup.file_sets` and `OutputGroup.inline_files`. (cherry picked from commit ff1f674)
Remove sdkcompat and platformsdk files
Fixed in IntelliJ here JetBrains/intellij-community@8d0a816
* Update changelog for v2024.08.27 release Please let me know of any important changes that you want to make visible by adding to the Change log. * Update changelog for v2024.08.27 release * Update changelog for v2024.08.27 release
Adds a CI runner for Mac. Soft failure for now.
It was required to provide backward compatiblity with 212
If we drop 221, all the implementations will be the same
* [#6664] Add `blaze mod ...` runner implementation - 2/n * Revert unnecessary change * javadocs * More comments * Skip using asMap * Update copyright and use project local output file * better name + copyright years
(cherry picked from commit 15a700f)
…Kotlin toolchains the `_toolchain` attribute is removed by `rules_kotlin` and `_cc_toolchain` attribute is planned to be removed by `rules_cc`. This change uses the new approach of aspect to toolchains propagation based on toolchain types instead. This feature is available in Blaze but not in all Bazel versions. Therefore, we keep using the old attribute-based approach for Bazel as the toolchain attributes will still be there for Bazel. (cherry picked from commit 7e7f940)
Modify copybara to get proto rules from protobuf (cherry picked from commit be5aa2e)
The BEP may now be configured to report files inline in the `TargetComplete` event on a per-output group basis, if the flag `--experimental_build_event_output_group_mode` is set appropriately. The `.proto` file references the correct flag name now. h/t to @sluongng for pointing out this discrepancy. RELNOTES: n/a (cherry picked from commit c4431be)
(cherry picked from commit d462c33)
A comment contains a warning that there should be at least two packages found in order to provide user a choice. However in some cases there is only a single package to add. For this reason, we stop the lookup if it reaches project root, but we don't add a package automatically, so a user can always reject the change. closes #6966
* Update changelog for v2024.11.05 release
* Use bazel icon for plugin logo We'd like to make plugin more discoverable in the search output on the marketplace and also make its tile look nice on the staff-picked plugins page. approved by @meisterT by email * Adjust icon size Marketplace and IntelliJ platform require 40x40 size * Minor adjustment from designer after rough resizing Removed some pixelness on the sides when scaled to 40x40
* 2024.3 update for plugins switch from 241 + 242 to 242 + 243 * clion: update SDK to 2024.3 Beta
* fixed multiple registrations * fixed notification show for files in a different project model * Rename .java to .kt * changes for 243 * added read action * created service for CLionNotificationProvider * added psw status to simple integration test * Revert "added psw status to simple integration test" This reverts commit c2906ad. Let's wait with this until we drop 241. Don't want to introduce sdk compat for tests.
* Update .bazelrc * Update .bazelversion
Co-authored-by: Mai Hussien <[email protected]>
Co-authored-by: Mai Hussien <[email protected]>
* fix: Support bazel 8 and `--noenable_workspace` mode closes #6984
* Fix querysync widget for remote dev * Fix
Removed the check for GENERIC language class when determining if Java is enabled. This change ensures that only the presence of JAVA language class sets the "isJavaEnabled" flag to true.
Previously, the condition to load rules_java was based on the "additional languages" field, which led to issues as Java is always present in IntelliJ (unlike PyCharm). This change modifies the condition to explicitly check if rules_java is actually loaded in the project, ensuring proper handling of non-Java projects in IntelliJ.
* feat: Starlark Debugger Gutter Icons
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )