Parent run not more present in i.e. after_node_run

[bf-malefiz]

Description

When trying to do a nested mlflow run in after_node_run hook the parent run is not active anymore. It worked like a few days ago and my pipelines were nested in the main run defined by the pipelinename.

Context

Goal to achieve is to use the created main MLflowHook with it's pipelinename by using the CLI and create child runs for different nodes.

Steps to Reproduce

I build a simple spaceflight env to reproduce this behaviour here: bf-malefiz/spaceflights-mlflow

The hook sets a tag for before_pipeline_run() and after_node_run() wihtout starting a new one, using the current active. In addition after_node_run creates a nested run.

Expected Result

set_tags without creating a child run should set both tags into the parent/main run
creating a nested run in after_node_run should use the main hook created from the runner

Actual Result

Main mlflow run gets closed and mlflow.active_run() in after_node_run returns None.
A new run with default mlflow option random_name gets created

Your Environment

• kedro and kedro-mlflow version used (pip show kedro and pip show kedro-mlflow):
  Name: kedro
  Version: 0.19.11

Name: kedro-mlflow
Version: 0.14.0

• Python version used (python -V):
  Python 3.13.1
• Operating system and version:
  Win11 Pro 24H2

Does the bug also happen with the last version on master?

Yes

[bf-malefiz]

Additional Info:

I'm trying to do a workaround with creating my own parent by closing and deleting the inital parent. When I instantiate them in before_pipeline_run, the new run gets closed as well. Parents and childs created after Next Node in excecution order will persist.

[Galileo-Galilei]

This is likely a bug of kedro==0.19.11. See #624 and slack. For now, my only advice is to downgrade to kedro==0.19.10, I'll keep you posted.