| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
There's no lexer for `grammar` supported by Jekyll, custom styles such as
`{.good}` are also not supported.
PiperOrigin-RevId: 178615029
|
|
|
|
|
|
|
|
|
|
| |
Make sure the actual binary recieves exactly the same argument passed to
Windows exe launcher.
Fixed https://github.com/bazelbuild/bazel/issues/4001
Change-Id: I5db2d7c2f78de8865abc04a2d5b65d69685d43db
PiperOrigin-RevId: 178610493
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178609245
|
|
|
|
|
|
|
| |
There's no lexer for `grammar` supported by Jekyll, custom styles such as
`{.good}` are also not supported.
PiperOrigin-RevId: 178607733
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/4262
A specific browser view width range causes the navigation bar to be stacked on top of the documentation content, therefore requiring a bit of scrolling to get to it.
This fix changes col-lg-* to col-md-*, which reduces the view width threshold at which the columns are restyled using `@media queries`.
Tested locally on Chrome & Safari. This is also testable by going to the production site and changing the CSS classes in the inspector.
Closes #4263.
PiperOrigin-RevId: 178605473
|
|
|
|
|
|
|
|
|
| |
passes.
Fixes #4268 .
RELNOTES: None.
PiperOrigin-RevId: 178604877
|
|
|
|
|
|
|
|
|
|
|
|
| |
MiddlemanFactory wants to check if the middleman inputs set is empty
or singleton. A NestedSet can answer both queries efficiently if the
right APIs are used.
My ultimate goal here is to avoid the expansion of runfiles artifacts
nested sets until execution.
Change-Id: I29a269df757ef41b1410bbb492cf24c926df6114
PiperOrigin-RevId: 178600943
|
|
|
|
|
|
|
| |
Also remove a TODO that was addressed in unknown commit.
RELNOTES: None
PiperOrigin-RevId: 178489151
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178448614
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178426166
|
|
|
|
|
|
|
| |
statistics to SpawnResults, and add cumulative getters for these in ActionResults.
RELNOTES: None.
PiperOrigin-RevId: 178426142
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, if the default_value is not set, but the flag
has been given a value by a configuration transition, that value
is used and no error is produced.
If the default_value is not set and the flag has not been given
a value by a configuration transition, the rule produces an
error (as it did before, but now the error is different).
config_feature_flags with default_values behave as they did before.
(use the default value if no configured value is set, otherwise use
the configured value)
Also transition the Optional used in feature flags from Guava to
Java 8.
RELNOTES: config_feature_flag's default_value is optional. It is
only an error to have a config_feature_flag with no default_value
if that config_feature_flag has not been set in the configuration
it is being evaluated in.
PiperOrigin-RevId: 178418907
|
|
|
|
|
|
| |
This implementation requires adding an interned list of LabelAndConfiguration objects to each RuleConfiguredTarget ('implicit' is an attribute describer, not a dep describer so filtering needs to happen while attribute information still exists).
PiperOrigin-RevId: 178411882
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178408662
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 178407067
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178406494
|
|
|
|
|
|
|
|
| |
aapt2 always gets the complete, unfiltered resources, and then filters them in
execution. Save time by not uselessly filtering in analysis.
RELNOTES: none
PiperOrigin-RevId: 178397137
|
|
|
|
| |
PiperOrigin-RevId: 178384991
|
|
|
|
|
|
| |
properly executable shell and correct test outputs.
PiperOrigin-RevId: 178376681
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This breaks downstream projects and blocks Bazel's 0.9.0 release. See https://github.com/bazelbuild/bazel/issues/4249 for more information.
*** Original change description ***
Move override check to the createAndOverrideRule function
So we actually test for override also from skylark repositories.
Fixes #3908.
Change-Id: I7650a17834a6915a73c89df46989f72aa2f56920
PiperOrigin-RevId: 178370143
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 178369060
|
|
|
|
|
|
|
| |
This is now possible because the Bazel release now supports TemplateVariableInfo.
RELNOTES: None.
PiperOrigin-RevId: 178360631
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: The flag --incompatible_list_plus_equals_inplace is removed, its
default behavior is preserved. += on lists now always mutates the left hand
side.
PiperOrigin-RevId: 178359047
|
|
|
|
|
|
|
|
|
| |
flag.
Add check to test options, default value of testFilter is null.
RELNOTES: None
PiperOrigin-RevId: 178337368
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's possible for a change in the configuration to result in multiple
visits to a particular target, but as long as each visit has a unique
configuration (relative to other visits to that target) and the cycle
is eventually broken (i.e., one of the targets in the cycle does not
depend on the next target in the cycle if the configuration satisfies
some property), this is perfectly buildable.
Or, in other words, it's okay to have a cycle in the target graph as
long as it is not also a cycle in the _configured_ target graph.
This test is to confirm this property.
RELNOTES: None.
PiperOrigin-RevId: 178303838
|
|
|
|
|
|
|
|
|
|
|
| |
This covers all builtins in classes that use SkylarkSignatureProcessor#configureSkylarkFunctions. Generally this means things you define with @SkylarkSignature.
It is now an error to call configureSkylarkFunctions multiple times for the same class. It should only be called in static initializers.
Runtime's static knowledge of builtins has been factored into Runtime.BuiltinRegistry.
RELNOTES: None
PiperOrigin-RevId: 178295926
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel-toolchains/releases/tag/b49ba36
PiperOrigin-RevId: 178294425
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178292524
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, aapt2 always gets all resources, even the filtered ones. As such,
always do density filtering, even if input to aapt2 says we don't have to.
We don't need to worry about not passing resource configuration filtering
information - it's already passed to aapt and aapt2 (since aapt is stricter
than the resource filtering in android_ide_common that is used to filter in
analysis, and also needs resource configuration filters to generate
pseudolocalized resources).
RELNOTES: none
PiperOrigin-RevId: 178282329
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Automated rollback of commit d6736496f0e1c35b7567f331988997892e32dfda.
*** Reason for rollback ***
broken test
*** Original change description ***
Report empty query results.
PiperOrigin-RevId: 178280711
|
|
|
|
|
|
|
|
|
| |
RELNOTES: None.
R_FUTURE=juliexxia
CC=blaze-firehose+cl
DELTA=0 (0 added, 0 deleted, 0 changed)
DELTA_BY_EXTENSION=sh=0
PiperOrigin-RevId: 178277209
|
|
|
|
| |
Change-Id: I5fe0abbd71488a624f1470d66bf6839e884bba8c
|
|
|
|
|
|
|
| |
RELNOTES:
Using `+`, `|` or `.union` on depsets is now deprecated. Please use the new
constructor instead (see https://docs.bazel.build/versions/master/skylark/depsets.html).
PiperOrigin-RevId: 178262338
|
|
|
|
| |
PiperOrigin-RevId: 178262335
|
|
|
|
| |
PiperOrigin-RevId: 178250626
|
|
|
|
|
|
|
|
|
|
|
| |
This is necessary bacause //tools/jdk:current_host_java_runtime is implemented in Skylark, and we don't (and shouldn't) have a way to create MiddlemanProvider from there.
However, we are planning to move to the the java_runtime_alias/java_host_runtime_alias rules as the exclusive representation of the javabase, so we need to be able to make one from Skylark.
Previously, this wasn't a problem, because if the javabase was a filegroup (like //tools/defaults:jdk), the path to the Java binary was taken from the configuration and the middleman from the filegroup, but since we are removing that information from the configuration, we can't do that anymore.
RELNOTES: None.
PiperOrigin-RevId: 178242307
|
|
|
|
|
|
|
| |
Addresses GitHub issue #4244 "Skylark API page is not available."
RELNOTES: None.
PiperOrigin-RevId: 178239595
|
|
|
|
|
|
|
|
|
|
| |
Designed here:
https://docs.google.com/document/d/1hK2mWl3TYNL9oJYX_S020TKkXZvBw1aBoYERvTHVyfg/edit
Fix https://github.com/bazelbuild/bazel/issues/3402
Change-Id: I9beff94d8b85ffeb4e46e0959c8f5ed4ef9c6268
PiperOrigin-RevId: 178238408
|
|
|
|
|
|
|
|
|
|
|
|
| |
JavaSkylarkApiProvider will be deprecated soon and replaced by JavaInfo.
Methods exposed:
getCompilationInfoProvider()
getTransitiveExports()
Changed signature of JavaCommon methods to accept JavaInfoBuilder.
RELNOTES:none
PiperOrigin-RevId: 178229835
|
|
|
|
|
|
|
| |
We don't put the toolchain identifier in directory names anymore.
RELNOTES: None.
PiperOrigin-RevId: 178229693
|
|
|
|
|
|
|
|
| |
Let's not expose middlemen to Skylark if we can help.
RELNOTES[INC]: The ctx.middle_man function is not supported anymore.
PiperOrigin-RevId: 178226393
|
|
|
|
|
|
|
|
| |
Sounds a bit more neutral than either the username of an actual person (Ulf, in
this case) or the abbreviation for "J. Random Luser".
RELNOTES: None.
PiperOrigin-RevId: 178224013
|
|
|
|
|
|
|
| |
generating another temporary directory name instead of throwing an exception.
RELNOTES: None.
PiperOrigin-RevId: 178190769
|
|
|
|
| |
PiperOrigin-RevId: 178176824
|
|
|
|
|
|
|
| |
In particular, provide all of the statistics available from the getrusage() system call.
RELNOTES: None.
PiperOrigin-RevId: 178162687
|
|
|
|
|
|
|
|
| |
../ziputils/DexMapper.
RELNOTES: None.
PiperOrigin-RevId: 178153254
|
|
|
|
|
|
|
| |
This avoids having to inline a bunch of default values when you only want to change one flag.
RELNOTES: None
PiperOrigin-RevId: 178148057
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178134833
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178130422
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks rapid candidate creation
*** Original change description ***
This and further changes may contain minor modifications to BUILD files that don't serve any apparent purpose. The reason for these changes is that we're switching from checked-in BUILD files to generated BUILD files, and there may be small differences between these files.
RELNOTES: None
PiperOrigin-RevId: 178120126
|