Potentially confusing print by YAML checker when checking a loader is first in the pipeline

Open
#515 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start in httomo/yaml_checker.py around lines 102-122, where the checker verifies that the first pipeline method is a loader and prints its success message. Make the message describe only that first-method check, then verify that it remains clear when another loader validation, such as duplicate-parameter detection, fails.

Written by the indexing model from the issue text.

Description

There's a check that is making sure that the first method in the pipeline YAML file is a loader:https://github.com/DiamondLightSource/httomo/blob/2e15a80e8e96753bc8a0d13285209cdbd9a56434/httomo/yaml_checker.py#L102-L122

If the check passes, the message printed is: https://github.com/DiamondLightSource/httomo/blob/2e15a80e8e96753bc8a0d13285209cdbd9a56434/httomo/yaml_checker.py#L120

However, in the event that:

  • this check passes
  • but other checks fail in the loader (such as a duplicate parameter)

this message being printed is confusing, because "loader check successful" implies that the loader config is error-free, but in reality this is not the case.

I think the message should be updated to be more specific in stating that the check for the first method being a loader was successful, to avoid such confusion in cases where the check passes but other checks that involve the loader fail. Maybe something like:

Loader first in pipeline check successful
Dominant language
Python
Stars
10
Forks
5
Avg merge
5d 17h
Merged PRs (30d)
1

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 DiamondLightSource/httomo

All issues in DiamondLightSource/httomo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.