Closed Pitasi closed 4 months ago
[!WARNING]
Rate Limit Exceeded
@Pitasi has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 46 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](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between a7e892f480f6b9e09bb42e8b94d08f05e52c0e3d and 1650686e2f35950417354eac838f371760ca58db.
The recent updates include the addition of a GitHub Actions workflow for linting and testing a Go project, modifications to the lexer for better string tokenization, and adjustments to tests to reflect these changes. Specifically, the lexer now returns a boolean indicating string validity, and tests for unterminated strings expect an ILLEGAL
token. Some tests were commented out due to unsupported mixed-type comparisons.
File | Change Summary |
---|---|
.github/workflows/shield.yml | Introduced a GitHub Actions workflow for linting and unit testing a Go project in the "shield" directory. |
shield/internal/evaluator/evaluator_test.go | Commented out two test cases involving mixed string to integer comparisons. |
shield/internal/lexer/lexer.go | Modified readString method to return a tuple of string and boolean for validity. |
shield/internal/lexer/lexer_test.go | Updated TestUnterminatedString to expect ILLEGAL token type and literal value " . |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
I merged some PR that broke shield's unit tests. In this PR I add a new github action to ensure this doesn't happen again, and fix the broken tests :)
Summary by CodeRabbit
New Features
Bug Fixes
Tests