Repository navigation
Phase 9/10: marketplace docs/E2E and tool/usage ledger instrumentation - #507
Merged
Merged
Conversation
- guard the optional billing-alert import in conftest - fix the alert test module-level skip and syntax - skip budget-alert tests until AyinkxLab#470 lands - fix email service docstring and import formatting
Record generate, code-action, and file-analysis completions as tools ledger rows with user, conversation, provider/model, and token metadata. Instrumentation is best-effort and never breaks the tool response.
Add 'flask usage backfill' with bounded keyset pagination, dry-run and JSON counts. Historical Message token columns are copied without being modified, and re-runs skip rows that were already backfilled.
…ab#423) Exercise the local catalog, install/enable endpoints, dependency ordering, trust refusal, event dispatch, and rollback without network access.
…#426) Document catalog, discovery, trust, network allowlist, execution, and catalog cache behavior in README, .env.example, and the plugin guide. Safe fail-closed defaults are called out explicitly.
|
@arike-tech Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
Author
|
Verification on the pushed branch (
The four issue-specific areas are covered by |
# Conflicts: # app/services/usage_ledger.py # tests/conftest.py # tests/test_usage_ledger.py
Contributor
Author
|
Conflict resolved by merging latest upstream Resolutions:
Verification after merge:
The PR is now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements four accepted Stellar Wave issues in one branch/PR.
README.md,.env.example, anddocs/plugins.md./tools/generate,/tools/code, and/tools/analyzecompletions in the usage ledger (source=tools), including user/conversation scope, provider/model, and token counts. Instrumentation is best-effort and still supports providers/test doubles that only implementcomplete.flask usage backfillwith keyset-paged batches,--limit,--dry-run, and--json. It copies historicalMessagetoken columns into ledger rows without modifying messages, and re-runs skip rows that were already backfilled.Test plan
python -m pytest tests/test_tools.py tests/test_usage_ledger.py tests/test_marketplace_e2e.py -qpython -m pytest tests/test_notifications.py tests/test_docs_links.py tests/test_alerts.py -qpython -m pytest -q --ignore=tests/test_migrations.pypython -m pytest tests/test_migrations.py -qpython -m ruff check .python -m black --check .Notes
main: optionalalerts/budget_alertsservices are guarded until their implementations land, and two recent formatting issues are fixed. Without this,pytestandruff check .fail before reaching these changes.Closes #423
Closes #426
Closes #431
Closes #434