Make it a fatal error when glob matches nothing
Open
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently you get a warning like
`[--:--:--][ ][ main:core activity ] WARNING No elements matched the glob expression: components/builbox-*.bst`.
This is nonsense. BuildStream completely unnecessarily initializes caches etc after this when this is clearly an error state.
Contributor guide
Research direction
Search the BuildStream code for the warning text and the glob-matching entry point. Change the no-match case to fail as a fatal error before unnecessary cache initialization, then verify that unmatched globs no longer continue with a warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100