Skip to content

Fix stem_memory coverage reporting and raise threshold#16

Merged
kingwill101 merged 1 commit intomasterfrom
fix/stem-memory-coverage-reporting
Feb 24, 2026
Merged

Fix stem_memory coverage reporting and raise threshold#16
kingwill101 merged 1 commit intomasterfrom
fix/stem-memory-coverage-reporting

Conversation

@kingwill101
Copy link
Owner

@kingwill101 kingwill101 commented Feb 24, 2026

Summary

  • add stem_memory unit tests that exercise every factory in memory_factories.dart
  • cover both broker dispose paths (InMemoryBroker.dispose and fallback Broker.close)
  • raise stem_memory workflow coverage threshold from 0 to 80

Verification

  • cd packages/stem_memory && dart test
  • cd packages/stem_memory && dart test --coverage=coverage --fail-fast
  • cd packages/stem_memory && dart run coverage:format_coverage --lcov --in=coverage --out=coverage/lcov.info --report-on=lib
  • cd packages/stem_memory && dart run ../../tool/coverage/coverage_badge.dart --lcov coverage/lcov.info --out coverage/coverage.json --min 80

Closes #14

@coderabbitai
Copy link

coderabbitai bot commented Feb 24, 2026

Warning

Rate limit exceeded

@kingwill101 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 359eb2b and 8d13f49.

📒 Files selected for processing (2)
  • .github/workflows/stem_memory.yaml
  • packages/stem_memory/test/unit/memory_factories_test.dart
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/stem-memory-coverage-reporting

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

Package publishing

Package Version Status Publish tag (post-merge)
package:stem 0.1.1 ready to publish stem-v0.1.1
package:stem_adapter_tests 0.1.1 ready to publish stem_adapter_tests-v0.1.1
package:stem_builder 0.1.0 ready to publish stem_builder-v0.1.0
package:stem_cli 0.1.0 already published at pub.dev
package:stem_memory 0.1.0 ready to publish stem_memory-v0.1.0
package:stem_postgres 0.1.0 already published at pub.dev
package:stem_redis 0.1.1 ready to publish stem_redis-v0.1.1
package:stem_sqlite 0.1.1 ready to publish stem_sqlite-v0.1.1

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

@kingwill101 kingwill101 merged commit a660d09 into master Feb 24, 2026
4 checks passed
@kingwill101 kingwill101 deleted the fix/stem-memory-coverage-reporting branch February 24, 2026 14:10
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.

Fix stem_memory coverage reporting in CI

1 participant