Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

PipelineRun.getSteps returns list of Step objects, not StepRun

Open
#1,933 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, jupyter-notebook, python

Research direction

Start with the reported azureml-sdk[notebooks] 1.52.0 reproduction on Ubuntu and run the PipelineRun and find_step_run snippet from the issue. Check the actual returned object types against the documented API and verify whether get_output_data is available. Done means the documented return type and the usable output methods agree.

Written by the indexing model from the issue text.

Description

  • Package Name: azureml-sdk[notebooks]
  • Package Version: 1.52.0
  • Operating System: Ubuntu 20.04.4 LTS
  • Python Version: 3.9.5

Describe the bug
When using function getSteps() of the class azureml.pipeline.core.PipelineRun, the returned object is a list of Step objects, not StepRun objects as described in the documentation.

To Reproduce
Steps to reproduce the behavior:
pipe_run = PipelineRun(experiment=exper, run_id=pipeline_runs[0].get_details()['runId']) step_run = pipe_run.find_step_run('cold_start_handling_knn_step')[0] step_run.get_output_data('recommendations_all')

Expected behavior
I expect to get a list of StepRun objects from the function find_step_run, but get a list of Run objects. Therefore, I cannot get the output using the get_outputs or get_output_data functions as those are only available for the StepRun objects.

Screenshots
image

Dominant language
Jupyter Notebook
Stars
4.4k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/MachineLearningNotebooks

All issues in Azure/MachineLearningNotebooks

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.