Closed MichaelScofield closed 3 days ago
[!WARNING]
Rate limit exceeded
@tisonkun has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 42 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 a9bf8cafc550e1a4d12fa2eec6f100da1473bf7c and d5cb7ba48c90aea4f75b2520db74fe1af20e23c5.
The recent changes streamline the StartCommand
implementation in both frontend.rs
and standalone.rs
by reordering and modifying arguments in crucial methods. The FrontendBuilder::new()
method now receives an opts.clone()
argument first, while the Services::new()
method no longer clones the opts
argument. Additionally, invoking the build_servers()
method no longer requires the opts
argument, simplifying the method calls.
Files | Change Summary |
---|---|
src/cmd/src/frontend.rs |
FrontendBuilder::new() restructured to put opts.clone() first; opts.clone() removed from Services::new() . |
src/cmd/src/standalone.rs |
FrontendBuilder::new() restructured to include fe_opts.clone() first; fe_opts.clone() removed from Services::new() . |
tests-integration/src/standalone.rs |
Added opts.frontend_options() in FrontendBuilder::new() . |
In the land where code does grow,
Frontend builders start the show.
With opts up front, they lead the way,
Simpler servers come to play.
Services shed their cloning woes,
Through streamlined paths, the data flows.
[!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 74.07407%
with 7 lines
in your changes missing coverage. Please review.
Project coverage is 84.82%. Comparing base (
2665616
) to head (d5cb7ba
).
@MichaelScofield It's better to use an option to control this behavior and it's disabled by default.
@killme2008 The current behavior is unaffected, new influxdb tables are still nanosecond time index. This PR simply brings compatibility back, so I don't think there's a need for an option.
@killme2008 The current behavior is unaffected, new influxdb tables are still nanosecond time index. This PR simply brings compatibility back, so I don't think there's a need for an option.
Alignment and checking typically impact performance, often unnecessary.
In other words, the user may create a table with a millisecond time index, and ingestion with influxdb, which we want to prohibit.
@MichaelScofield We already discussed this before and have an agreement. Maybe you can discuss it directly with @fengjiachun . I have to sleep.
@killme2008 I have added an option for that.
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?
... so that other projects could modify the row insert according to their specific intention.
Checklist
Summary by CodeRabbit
These changes enhance the backend structure without affecting user-facing features directly.