Skip to content

suites: suggest import-harbor when a directory looks like Harbor tasks - #170

Merged
patsypppe merged 1 commit into
patsypppe:mainfrom
abu-tahir-0:fix/83-harbor-hint
Nov 8, 2026
Merged

patsypppe merged 1 commit into
patsypppe:mainfrom
abu-tahir-0:fix/83-harbor-hint

Conversation

@abu-tahir-0

Copy link
Copy Markdown
Contributor

What this changes

Closes #83.

load_suite already reports missing_suite_file when a directory has no suite.yaml. That issue's message now adds "this looks like Harbor tasks — run meridian import-harbor first" when task.toml is present at the dataset root, one directory down, or two — the layouts find_task_dirs accepts. The CLI prints every validation issue's message, so run, publish, gate and suite build-images all get the hint. A directory without a task.toml keeps the plain message.

How it was checked

  • make check passes (ruff, mypy --strict, unit tests) — except tests/unit/test_web_vectors.py, which fails identically on a clean main here (t_quantile differs in the last bit); unrelated to this change. The rest of the unit suite is 574 passed.
  • New behaviour has a test at the cheapest tier that can catch it, including the case that should fail: a Harbor layout gets import-harbor in the message, a plain directory does not, and both still report missing_suite_file.
  • make integration / make e2e — not needed for the loader; this change adds no runtime path.

Anything a reviewer should know

  • The hint is attached to the existing validation issue rather than a new code, so scripts keyed on missing_suite_file keep working.
  • The check duplicates the three-level discovery rule from importers/harbor.py rather than importing the importer into the loader; happy to share a helper if you would rather have one source of truth.

Pointing run or publish at a Harbor dataset used to fail with only "no suite.yaml", which says nothing about the command that converts it. The missing-suite-file issue now carries the hint when task.toml appears at the dataset root, one level down, or two. A plain directory stays hint-free.
@patsypppe

Copy link
Copy Markdown
Owner

nice jobs but make sure to get this task assigned to you next time and tell your approach before working on it. please read CONTRIBUTIONS.md. I will merge this one

@patsypppe
patsypppe merged commit 6ecbe97 into patsypppe:main Nov 8, 2026
6 of 7 checks passed
patsypppe added a commit that referenced this pull request Nov 8, 2026
…172)

A pull request from a fork gets a read-only token, so the Comment step
failed with 'Resource not accessible by integration' and turned a passing
gate red (seen on #170, where the verdict was pass). Skip the comment for
forks and always write the verdict to the job summary instead.


Claude-Session: https://claude.ai/code/session_017urKavHf7CSyMqnzeCCyoy

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Suggest import-harbor when given a Harbor directory

2 participants