Ah, realized this is from a test, so there could be a rule that’s not included in the runner… will look into that

OK, I got a bit further, but still stuck.. This works:

res = chroot_rule_runner.request(Targets, [UnparsedAddressInputs(["//src/python/foo:foo-dist"], owning_address=None)])

and gives me:

----------------------------- Captured stdout call -----------------------------
Targets([<class 'pants.backend.python.target_types.PythonDistribution'>(address=src/python/foo:foo-dist, alias='python_distribution', dependencies=None, description=None, entry_points=FrozenDict({'console_scripts': FrozenDict({'foo_tool': 'foo.bar.baz:Tool.main', 'bin_tool': '//src/python/foo/qux:bin', 'hello': ':foo-bin'}), 'foo_plugins': FrozenDict({'qux': 'foo.qux'})}), provides=foo, setup_py_commands=None, tags=None)])

However, the error is still there…

E           Engine traceback:
E             in select
E             in pants.backend.python.goals.setup_py.generate_chroot
E             in pants.engine.internals.graph.transitive_targets
E             in pants.engine.internals.graph.resolve_targets (src/python/foo:foo-dist)
E             in pants.engine.internals.graph.resolve_unexpanded_targets (src/python/foo:foo-dist)
E             in pants.engine.internals.graph.resolve_dependencies (src/python/foo:foo-dist)
E             in pants.backend.python.target_types_rules.inject_python_distribution_dependencies (src/python/foo:foo-dist)
E             in pants.backend.python.target_types_rules.resolve_python_distribution_entry_points
E           Traceback (no traceback):
E             <pants native internals>
E           Exception: Could not find a rule to satisfy Get(Targets, UnparsedAddressInputs, UnparsedAddressInputs(values=('//src/python/foo/qux:bin',), relative_to='src/python/foo')).

From the code under test:

targets = await Get(Targets, UnparsedAddressInputs([ref], owning_address=address))

Do I simply just miss some required QueryRule()`s for the rule runner?

Yep, found it. Took a while to realize that I had to add QueryRules that matched the actual Get calls…

or so I thought…. hmmm

ok, I got this message:

E       Exception: No installed QueryRules can compute Targets given input Params(UnparsedAddressInputs), but it can be produced using:
E         Params(Addresses)
E         Params(UnexpandedTargets)

when I have these QueryRule()s

QueryRule(Addresses, (UnparsedAddressInputs,)),
            QueryRule(UnexpandedTargets, (Addresses,)),
            QueryRule(Targets, (UnexpandedTargets,)),

So, if I add a QueryRule() going from UnparsedAddressInputs to Targets, it works when I use the rule runner request, but I can’t get any QueryRule to work when I try to use await Get()…

will take a break, back later, or tomorrow 🙂

is there some reason that this

Get

might not have been detected in your

@rule

body? had it been extracted into a separate function perhaps?

Ah, that could be it

Yes, my Get() call is in a separate function

i’ll see if we can improve the runtime error message to mention this case.

reading up on the docs to see if I could (should?) have resolved it that way.. nit-pick is the mention of the extinct engine channel..

ask for help in the #engine channel …

https://www.pantsbuild.org/docs/rules-api-concepts

And, well yes, I could’ve.. as it was on the very first line on the section for

await Get

..

In addition to requesting types in your rule’s parameters, you can request types in the body of your rule.

This could be highlighted for additional emphasis, though (although the new improved error message makes this less important) 🙂

I’m not used to find documentation in general to be so well covered, so kudos to you on that 💯