ci: shared gh-ci scripts: reject non-Linux matrix cells, CRLF METADATA, matrix.py parsing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 53/100
Research direction
Start by reading the shared gh-ci scripts and their vendored copies, especially matrix.py, build.py, and intel-ci.yml; the issue does not give their paths. Check how matrix cells are parsed, how add_requirements reads METADATA, and how the source scripts are re-vendored. Done means non-Linux cells are rejected, the listed parsing cases and CRLF line endings are handled, and the updated scripts are vendored into dokimi.
Written by the indexing model from the issue text.
Description
Follow-up from the review of #378 (latent for dokimi, which builds on Linux only):
intel-ci.yml:runs-onignoresmatrix.platform. Makematrix.pyreject non-Linux cells, rather than mapping them, until a non-Linux runner is wanted.build.py add_requirements: handle CRLF line endings inMETADATA.matrix.py: a skip line with a trailing comment;>3.10specifiers; FreeBSD classifier.
These live in the shared gh-ci scripts, so fix them at the source and re-vendor.
- Dominant language
- Python
- Stars
- 11
- Forks
- 9
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 318
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/dokimi
-
dependencies
Difficulty 3/5 1-2 days Newbie friendliness 49/100
Maintainers usually reply within 1 day
-
repo: Bash reads dropped where the shell could not have moved (conservative limits of #369)Possibly taken @antonwolfy claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
intel/dokimi#374 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
eval reference: stamp a digest of the questions file so headroom catches an edit at the same pathOpen
Difficulty 3/5 1-2 days Newbie friendliness 32/100
Maintainers usually reply within 1 day
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
neilsh/stunt-reel#220 ·
Maintainers usually reply within 1 day
-
[Issue]: use_fp4_cache is accepted but ignored; the launcher always writes FP8 recordsPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: cli priority: p3 size: S type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
finos/open-resource-broker#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days