fix(fuzz): generate valid string

[WenyXu]

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?

Generate valid string for column default value

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.

Summary by CodeRabbit

• Tests
  • Improved random value generation by utilizing WordGenerator.
  • Reduced wait time for region distribution checks from 120 to 60 seconds, enhancing test efficiency.
  • Updated log message for region distribution to improve consistency in output format.

[coderabbitai]

Walkthrough

The recent changes involve importing a new WordGenerator, altering a function call in ir.rs to use this new import, refining a log message format in migration.rs, and optimizing the wait time and loop order in fuzz_migrate_mito_regions.rs. These changes collectively aim to enhance functionality, clarify log outputs, and optimize test performance.

Changes

Files	Change Summary
tests-fuzz/src/ir.rs	Added WordGenerator import and modified a function call to use Some(&WordGenerator) as an argument.
tests-fuzz/src/utils/migration.rs	Updated log message format from "Region Distribution: {:?}" to "region distribution: {:?}".
tests-fuzz/targets/migration/fuzz_migrate_mito_regions.rs	Reduced wait time from 120 to 60 seconds and adjusted loop order for procedure_ids.

Poem

In the code's embrace, a change we see,
Words now born from a generator's spree.
Logs refined with a subtle touch,
Wait times halved, not lingering much.
A rabbit's joy at tweaks so bright,
Hopping through data, morning 'til night. 🐇✨

---

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d917521 and d726f7d.

Files selected for processing (1)

• tests-fuzz/src/ir.rs (2 hunks)

Additional comments not posted (2)

tests-fuzz/src/ir.rs (2)

43-43: The new import statement for WordGenerator looks good.

The addition of WordGenerator is appropriate for generating valid strings.

---

454-458: The changes to partible_column_options_generator are correct.

Passing Some(&WordGenerator) to generate_random_value ensures valid strings are generated for the column default value.

[fengjiachun]

LGTM

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d726f7d and b98d9e8.

Files selected for processing (2)

• tests-fuzz/src/utils/migration.rs (1 hunks)
• tests-fuzz/targets/migration/fuzz_migrate_mito_regions.rs (1 hunks)

Files skipped from review due to trivial changes (2)

• tests-fuzz/src/utils/migration.rs
• tests-fuzz/targets/migration/fuzz_migrate_mito_regions.rs

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 84.69%. Comparing base (03c933c) to head (b98d9e8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4281      +/-   ##
==========================================
- Coverage   84.96%   84.69%   -0.27%     
==========================================
  Files        1058     1058              
  Lines      188055   188059       +4     
==========================================
- Hits       159780   159284     -496     
- Misses      28275    28775     +500