Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixing listener memory leak - issue #222 #223

merged 1 commit into from Feb 2, 2023


Copy link

@jaredwray jaredwray commented Feb 2, 2023

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fixing listener memory leak - issue #222

Copy link

codecov bot commented Feb 2, 2023

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (9a448c6) compared to base (39cd197).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #223   +/-   ##
  Coverage   100.00%   100.00%           
  Files            2         2           
  Lines          161       162    +1     
  Branches        38        38           
+ Hits           161       162    +1     
Impacted Files Coverage Δ
src/index.ts 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@jaredwray jaredwray merged commit 1b38d5a into main Feb 2, 2023
7 checks passed
@jaredwray jaredwray deleted the fixing-listener-memory-leak---issue-#222 branch February 2, 2023 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant