Hey team, Any insights into the error `Node my_nod...
# questions
p
Hey team, Any insights into the error
Node my_node_name: my_node_name() -> None failed with error: Nested.from_tree() missing 1 required positional argument: 'node'
? This specific kedro project is deployed to Databricks using wheels and entry points and was working fine in the past, except when I add this new pipeline to it (which by the way runs fine locally). Since debugging the wheel pipeline in Databricks seems quite hard, I would appreciate any insight
j
hi @Pedro Sousa Silva! any chance you could share the full traceback? so that we see where the error is coming from
p
Hey @Juan Luis. That's exactly my problem, Databricks execution of a wheel does not print out the full traceback and I can't even find it in the logs (appreciate if you know how to grab that info). All I can see is that this error message comes from
node.py:386
👀 1
image.png
j
ugh that's interesting, I would have expected a traceback there. have you ever seen this folks @Nok Lam Chan @Dmitry Sorokin?
e
Hi @Pedro Sousa Silva, here are some thoughts on how you may proceed with debugging to provide us with some more details. • Isolate the pipeline you’ve added and check if it’s running • Check if other nodes are running successfully to understand if it’s happening with just one node • Share a definition of a problematic node/pipeline part with us if possible
p
Hey @Elena Khaustova, thanks for the suggestions. I already followed that process and eventually isolated the specific nodes failing - here's their definition:
👀 1
n
Is there no traceback provided? If you can disable the rich logger by going to
logging.yml
and change
rich
->
console
👀 1
p
so looks like that just de-formats the output but still brings no traceback?
n
Have you seen the traceback before? I don’t know what is expected in the databricks UI normally.
p
So you get it in notebooks but apparently not in workflow executions
In any case, I just pip installed the wheel and replicated the kedro pipeline in a notebook and was able to get the traceback - turns out it has nothing to do with kedro but rather with a random library i'm using (openpyxl) - sorry about that, I was positive this would be some kedro internal. Thanks guys! @Juan Luis @Nok Lam Chan @Elena Khaustova
👍🏼 1
👍 1
j
thanks @Pedro Sousa Silva! still, it's worrying that tracebacks don't appear in Databricks jobs... has anybody else found that situation? is that expected?