repo-eval.yml: Select tasks step crashes on a validate document with data null

Open Beginner friendly
#684 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python, yaml
Domain
ci-cd, tooling

Research direction

Start with .github/workflows/repo-eval.yml around line 206 and trace how the Select tasks step reads the validator's JSON. Run dokimi repo validate . --manifest /nonexistent.yaml --json to confirm the data: null case. Done when the step handles that output without raising a TypeError; the issue notes that main currently fails with a JSONDecodeError.

Written by the indexing model from the issue text.

Description

Raised in the review of PR #590 (intel/dokimi), thread PRR_kwDOVBg7g88AAAABXrLtSQ.d: https://github.com/intel/dokimi/pull/590

Found in PR #590 review. dokimi repo validate . --manifest /nonexistent.yaml --json writes "data": null; the Select tasks step then raises TypeError on d["manifest"] (.github/workflows/repo-eval.yml:206). On main the step fails with JSONDecodeError instead. Pre-existing, outside the PR's lines.

Not fixed in PR #590: it is outside the lines that PR changes (another component, a design change, or too large for the round).

Dominant language
Python
Stars
39
Forks
13
Avg merge
1d 10h
Merged PRs (30d)
519

Getting set up

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 intel/dokimi

All issues in intel/dokimi

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.