plugins infrastructure brittle with spack
Open
Nobody has claimed this yet.
build
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
The plugins infrastructure and relative vs absolute paths logic is brittle with spack. Thanks @rbberger for finding this issue.
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.
Research direction
Start by locating the plugin infrastructure and the relative-versus-absolute path handling described in the issue, then reproduce the brittleness through a Spack-based build. Identify the failing path scenario, add regression coverage for it, and verify that the plugin setup works correctly with Spack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100