vectordotdev / vectordotdev/vector
Add check for memory leaks to CI
Open
Nobody has claimed this yet.
domain: ci
domain: reliability
domain: tests
have: nice
meta: idea
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
A check for memory leaks can be added to CI in order to detect leaks caused by native dependencies. It can be done in a way similar to how it was added to quick-js crate.
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 inspecting the repository's existing CI configuration and the linked quick-js crate change. Determine how a memory-leak check can cover native dependencies without disrupting normal CI runs. Done means CI reliably detects and reports memory leaks caused by those dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100