spec-parser run reports errors but exits with `0`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the spec-parser command using the linked GitHub Actions log, then trace how the Invalid Nature attribute in metadata None error is handled. The fix is done when this error causes the process to exit with a nonzero status while successful parsing still exits with 0; add or update a test if the repository provides one.
Written by the indexing model from the issue text.
Description
The current spec parser reports an error but does still exit with EXIT_SUCCESS. See for example https://github.com/spdx/spdx-3-model/actions/runs/7118823989/job/19382571564#step:5:25 with the log:
> Run cd spec-parser
WARNING : External property restrictions aren't yet handled properly, they are added to the description of the class.
WARNING : skipping ../model/Core/Properties/_property.md
WARNING : skipping ../model/Core/Vocabularies/_vocab.md
WARNING : External property restrictions aren't yet handled properly, they are added to the description of the class.
WARNING : External property restrictions aren't yet handled properly, they are added to the description of the class.
WARNING : External property restrictions aren't yet handled properly, they are added to the description of the class.
WARNING : External property restrictions aren't yet handled properly, they are added to the description of the class.
WARNING : Overwriting out_dir `/tmp/spec-parser.out`
ERROR : Invalid Nature attribute in metadata `None`
- Dominant language
- Python
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 spdx/spec-parser
-
spdx/spec-parser#214 · 5 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
spdx/spec-parser#207 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
spdx/spec-parser#204 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
spdx/spec-parser#203 ·
-
spdx/spec-parser#198 · 1 comment · 2 assignees ·
All issues in spdx/spec-parser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100