Skip to content

Conversation

@davidB
Copy link
Owner

@davidB davidB commented Jan 2, 2025

try to reproduce a possible memory leak see #191

@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2025

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ EDITORCONFIG editorconfig-checker 6 0 0.02s
✅ JAVASCRIPT standard 1 1 0 1.26s
✅ MARKDOWN markdownlint 1 0 0 0.24s
✅ MARKDOWN markdown-table-formatter 1 0 0 0.17s
✅ REPOSITORY checkov yes no 10.15s
✅ REPOSITORY dustilock yes no 0.0s
✅ REPOSITORY gitleaks yes no 0.27s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 9.39s
✅ REPOSITORY secretlint yes no 0.57s
✅ REPOSITORY syft yes no 1.17s
✅ REPOSITORY trivy-sbom yes no 0.07s
✅ REPOSITORY trufflehog yes no 1.53s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

@davidB davidB force-pushed the fix_memory_leak branch 2 times, most recently from 324734f to 757e6ea Compare January 2, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants