comment: address most of the comments

Author: aignas

python/private/sentinel.bzl

@@ -27,7 +27,7 @@ def _sentinel_impl(ctx):
     _ = ctx  # @unused
     return [
         SentinelInfo(),
-        # Also output ToolchainInfo
+        # Also output ToolchainInfo to allow it to be used for noop toolchains
         platform_common.ToolchainInfo(),
     ]
 

python/uv/private/lock.bzl

@@ -145,10 +145,7 @@ def _lock_impl(ctx):
             uv,
             python_files,
         ],
-        progress_message = "Creating a requirements.txt with uv: //{}:{}".format(
-            ctx.label.package,
-            ctx.label.name,
-        ),
+        progress_message = "Creating a requirements.txt with uv: %{label}",
         env = ctx.attr.env,
     )
 
@@ -189,6 +186,8 @@ _python_version_transition = transition(
 _lock = rule(
     implementation = _lock_impl,
     doc = """\
+The lock rule that does the locking in a build action (that makes it possible
+to use RBE) and also prepares information for a `bazel run` executable rule.
 """,
     attrs = {
         "args": attr.string_list(

tests/uv/lock/lock_tests.bzl

@@ -36,7 +36,7 @@ def lock_test_suite(name):
             "testdata/build_constraints2.txt",
         ],
         # It seems that the CI remote executors for the RBE do not have network
-        # connectivity. Is it only our setup or is it a property of RBE?
+        # connectivity due to current CI setup.
         tags = ["no-remote-exec"],
         out = "testdata/requirements.txt",
     )
@@ -46,7 +46,7 @@ def lock_test_suite(name):
         srcs = ["testdata/requirements.in"],
         out = "does_not_exist.txt",
         # It seems that the CI remote executors for the RBE do not have network
-        # connectivity. Is it only our setup or is it a property of RBE?
+        # connectivity due to current CI setup.
         tags = ["no-remote-exec"],
     )