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: add a bit more logging to help track down usage billing bugs #455

Merged
merged 3 commits into from
Jan 22, 2025

Conversation

travis
Copy link
Member

@travis travis commented Jan 14, 2025

For some reason some space snapshots have been missed in the past, despite seemingly being in the DB and showing up in dry run.

Also throw if the usage table queue gets an empty message - if this is happening I'd like to understand why, and I'm suspicious that some of our usage tracking issues are messages that are somehow being created with no records.

For some reason some space snapshots have been missed in the past, despite seemingly being in the DB and showing up in dry run.
Copy link

seed-deploy bot commented Jan 14, 2025

View stack outputs

remove one log line since it's already covered by a different line, and improve that line

throw an error rather than just returning silently if we receive an insert event with no records - I think this is an error, since I'm not sure when it could happen
@seed-deploy seed-deploy bot temporarily deployed to pr455 January 15, 2025 18:46 Inactive
@travis travis merged commit 5a7d707 into main Jan 22, 2025
3 checks passed
@travis travis deleted the fix/build branch January 22, 2025 00:15
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.

2 participants