You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lockfile detection believes that directories might be lockfiles.
How To Reproduce
> mkdir requirements.txt
> lsrequirements.txt
> phylum parseGenerating lockfile for manifest "./requirements.txt" using Pip…❗ Error: Lockfile generation failed! For details, see: https://docs.phylum.io/docs/lockfile-generationCaused by: package manager exited with error code 1: ERROR: Could not open requirements file: [Errno 21] Is a directory: '/path/to/requirements.txt'
This error message isn't very helpful....
> mkdir Cargo.lock
> phylum parse❗ Error: Is a directory (os error 21)
#1202 as a solution was discarded, since even checking for !is_directory still causes syscalls to lookup metadata for every lockfile, even if it doesn't cause failure for the GitHub App. Since this has never caused any issues in practice, there's no reason to slow down the GitHub App.
Activity
Ensure lockfiles are files
Ensure lockfiles are files
cd-work commentedon Aug 18, 2023
#1202 as a solution was discarded, since even checking for
!is_directorystill causes syscalls to lookup metadata for every lockfile, even if it doesn't cause failure for the GitHub App. Since this has never caused any issues in practice, there's no reason to slow down the GitHub App.Improve lockfile parsing errors
Improve lockfile parsing errors (#1204)