Weird. The dep cycle issue reported in #pantsd is only when the Protobuf dependency injection rules are triggered, and only when using transitive deps. When using transitive deps, the last line of the below doesn’t resolve properly. It gives back a reference to only one target, and the wrong target:

@rule
async def transitive_target(wrapped_root: WrappedTarget) -> TransitiveTarget:
    root = wrapped_root.target
    if not root.has_field(Dependencies):
        return TransitiveTarget(root, ())
    dependency_addresses = await Get[Addresses](DependenciesRequest(root[Dependencies]))

Unregistering the protobuf rule fixes it all.

As with the last bug, if the issue is only in pantsd equals/hash are the prime suspects. Has that class of issue been ruled out?

I think, as this fails without pantsd too.

Is

root[Dependencies]

legit? I though Dependencies were async now and had to be awaited.

root[Dependencies]

gets the

Dependencies

field, which stores a

sanitized_raw_value

. Then, you say

await Get[Addresses](DependenciesRequest(dependencies_field))

Oh.. can answer that from context. Dependencies must just be strings

Yes. Technically, the

sanitized_raw_value

is a

Tuple[Address, ...]

because of the

@addressable

mechanism