Report when a bad library causes an analysis worker to terminate due to a timeouts.
Open
Nobody has claimed this yet.
bug
dynamic analysis
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
Currently the analysis does not set any timeouts on how long an install and import is allowed to run.
This can allow a bad library to cause an analysis worker to block forever waiting for it to finish.
Contributor 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.
Research direction
Start by locating the analysis worker entry point and the code that installs and imports libraries. Determine how those operations can be bounded and how a timeout should be reported; done means a bad library cannot block the worker forever and the analysis records the timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100