Skip to content

fix: prevent potential memory leak by properly removing watcher references #2379

fix: prevent potential memory leak by properly removing watcher references

fix: prevent potential memory leak by properly removing watcher references #2379

Triggered via pull request October 18, 2024 17:32
@Aryan4884Aryan4884
opened #1307
Status Failure
Total duration 18s
Artifacts

lint-pr-title.yml

on: pull_request_target
Lint PR title
5s
Lint PR title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Lint PR title
Unknown release type "Fix" found in pull request title "Fix: prevent potential memory leak by properly removing watcher references". Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit
Lint PR title
The following actions use a deprecated Node.js version and will be forced to run on node20: amannn/action-semantic-pull-request@c3cd5d1ea3580753008872425915e343e351ab54, marocchino/sticky-pull-request-comment@3d60a5b2dae89d44e0c6ddc69dd7536aec2071cd. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/