Closed WenyXu closed 2 days ago
[!WARNING]
Rate limit exceeded
@WenyXu has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 5 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 5544797f96c225de8478d04fc44ffe3c74d98c46 and 034c4de6cc1f1091184b3a3ec1bd4baf7e359076.
The updates primarily involve integrating a new utility function, get_from_env_or_default_value
, which fetches configuration values from environment variables or defaults them to predefined values. This function and several associated constants have been employed across various fuzz testing target files to customize parameters such as column and row limits, enhancing flexibility and robustness in fuzz tests' execution.
Files / Groups | Change Summary |
---|---|
tests-fuzz/targets/fuzz_insert.rs |
Updated imports and added environment-based configuration for column and row limits. |
tests-fuzz/targets/fuzz_insert_logical_table.rs |
Added rows to FuzzInput , environment-based tables , and rows values, and updated insert_values function. |
tests-fuzz/targets/fuzz_alter_logical_table.rs |
Modified imports, added a new utility function and constant, and used them in arbitrary implementation. |
tests-fuzz/targets/fuzz_alter_table.rs |
Changed column generation in generate_create_table_expr to use new utility function and environment variable. |
tests-fuzz/targets/fuzz_create_table.rs |
Added new utility function and constant, updated FuzzInput struct to use environment-based column generation. |
tests-fuzz/targets/failover/fuzz_failover_mito_regions.rs |
Used new utility function for initializing fuzz testing parameters from environment variables. |
tests-fuzz/targets/unstable/fuzz_create_table_standalone.rs |
Updated FuzzInput to include tables field, generated number of tables based on environment variable. |
In the realm of fuzz, where bits do play, We've crafted a tune for variables' sway. With columns and rows from the env they derive, Our tests now dance, alive, alive! Tables and actions, dynamic, robust, In this code-tale, our trust we entrust. 🌟🐇
[!TIP]
Early access features: enabled
We are currently testing the following features in early access: - **OpenAI `gpt-4o` model for code reviews and chat**: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available. Note: - You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file. - Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide feedback and report issues. - OSS projects are currently opted into early access features by default.
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?
Attention: Patch coverage is 0%
with 6 lines
in your changes missing coverage. Please review.
Project coverage is 84.69%. Comparing base (
e531326
) to head (034c4de
). Report is 8 commits behind head on main.
Could you explain why we need to reduce the size of data insertion? @WenyXu
It's better to be configured by environment variables, and we can configure it larger in release ci and a smaller value for every PR.
Could you explain why we need to reduce the size of data insertion? @WenyXu
Just want to speed up the CI.
It's better to be configured by environment variables, and we can configure it larger in release ci and a smaller value for every PR.
Good point, I'm going to add this feature.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Reduce data insertion size of
fuzz_insert
&fuzz_insert_logical_table
targets.Checklist
Summary by CodeRabbit
New Features
Refactor
Chores