Invalid YAML in test_cpu suite rejected by yaml-cpp 0.9.0
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Start with tests/cpu/Config_tests.cpp around lines 6492-6502 and run the test_cpu suite against yaml-cpp 0.9.0 to reproduce the failure. Inspect the YAML fixture used by the test; done means test_cpu_exec completes without the YAML parsing error or segmentation fault.
Written by the indexing model from the issue text.
Description
https://github.com/NixOS/nixpkgs/pull/560590#issuecomment-5564165433
When built against yaml-cpp version 0.9.0, test_cpu_exec fails:
[ 129/1169] [Config / inactive_color_space_precedence ] - PASSED
/build/source/tests/cpu/Config_tests.cpp:6502:
FAILED: exception thrown from config = OCIO::Config::CreateFromStream(is): "Error: Loading the OCIO profile failed. yaml-cpp: error at line 25, column 1: plain value cannot start with flow indicator character"
Segmentation fault (core dumped) ./test_cpu_exec
If you want to continue using funky YAML in this test, then the continued lines of the array with more than just whitespace content must be indented. Example fix (without CLA signature): #2339
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 503
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No 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 AcademySoftwareFoundation/OpenColorIO
-
Inconsistent run-time library usage for locale handling breaks GPU code generation on some systems.Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AcademySoftwareFoundation/OpenColorIO#2351 · 2 comments ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AcademySoftwareFoundation/OpenColorIO#2329 ·
Maintainers usually reply within 4 days
-
Build failure on GCC/MinGW (MXE): std::ifstream constructor mismatch with Platform::filenameToUTF()Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AcademySoftwareFoundation/OpenColorIO#2283 ·
Maintainers usually reply within 4 days
-
Documentation
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AcademySoftwareFoundation/OpenColorIO#2280 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AcademySoftwareFoundation/OpenColorIO#2277 ·
Maintainers usually reply within 4 days
All issues in AcademySoftwareFoundation/OpenColorIO
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ml-explore/mlx-c#136 ·
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day