Fix lyrics analyzer rate limit #64
Merged
Conversation
This file contains 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
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.
Description
This PR fixes a bug with how rate limits are tracked for the lyrics analyzer command.
Every now and then, the user ID property would not be serialized correctly as a
ulongtype. Seems like it was on the CosmosDB side and not directly in the code? What I ended up doing to fix it was changing the type fromulongtostring.In addition, I added an intialization step for the
CosmosDbServiceto ensure that the database and containers exist and, if they don't, to create them at startup. Needed this for locally testing the changes.Type of change
Related issues