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

fix: stream monitoring #573

Merged
merged 1 commit into from
Oct 18, 2024
Merged

fix: stream monitoring #573

merged 1 commit into from
Oct 18, 2024

Conversation

fenos
Copy link
Contributor

@fenos fenos commented Oct 17, 2024

What kind of change does this PR introduce?

Feature

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

coveralls commented Oct 17, 2024

Pull Request Test Coverage Report for Build 11398937076

Details

  • 33 of 108 (30.56%) changed or added relevant lines in 5 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.1%) to 78.027%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/storage/backend/s3.ts 7 11 63.64%
src/internal/streams/monitor.ts 9 42 21.43%
src/internal/streams/stream-speed.ts 13 51 25.49%
Totals Coverage Status
Change from base Build 11380151542: 0.1%
Covered Lines: 13870
Relevant Lines: 17638

💛 - Coveralls

@fenos fenos force-pushed the monitoring/stream-monitoring branch from 0b464ef to 88fe58a Compare October 18, 2024 06:53
@fenos fenos merged commit f950fc4 into master Oct 18, 2024
1 check passed
@fenos fenos deleted the monitoring/stream-monitoring branch October 18, 2024 16:13
Copy link

🎉 This PR is included in version 1.11.16 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants