Follow up on 1094 - Windows Directory Resolver error for ALPMDB dir:. scan
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 954
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 48
Description
**Please provide a set of steps on how to reproduce the issue**:
See #1094: cataloging ALPM symlinks ends in an error condition on windows
`syft/pkg/cataloger/alpm/parse_alpm_db.go:110` <-- Windows is unable to resolve the directory correctly and this will end in an error condition. Previously it would result in a panic
**What you expected to happen**:
syft should scan ALPM DB
**Anything else we need to know?**:
Windows Path Based - Darwin/Linux works as expected
Contributor guide
Research direction
Start with syft/pkg/cataloger/alpm/parse_alpm_db.go:110 and issue #1094. Reproduce an ALPM database scan on Windows, then compare the path behavior with Darwin/Linux; done means syft scans the ALPM DB without a directory-resolution error or panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100