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

`no log keys matched prefix` error needs a remediation hint

Open
#21 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@sawka-harness is already working on this.

Since Jun 26, 2026.

Assessment

This issue has not been assessed yet.

Description

beta

Summary

modules/pipeline/execution_log.go:140–141 returns:

return fmt.Errorf("no log keys matched prefix %q", filterPrefix)

The user is left guessing whether the execution doesn't exist, the prefix is wrong, or the run produced no logs.

Suggested fix

return fmt.Errorf(
    "no log keys matched prefix %q — verify the execution ID is correct, that the run produced logs, and that the prefix matches the stage/step naming",
    filterPrefix,
)

Acceptance

  • Error updated.
  • Manual smoke: run with a known-bad prefix; observe the more helpful guidance.
Dominant language
Go
Stars
22
Forks
12
Avg merge
1d 2h
Merged PRs (30d)
37

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 harness/cli

All issues in harness/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.