Skip to content

Use unique DB name for Postgres test fixture#163

Open
leynos wants to merge 1 commit into
mainfrom
codex/use-unique-db-name-for-postgres-test-fixture
Open

Use unique DB name for Postgres test fixture#163
leynos wants to merge 1 commit into
mainfrom
codex/use-unique-db-name-for-postgres-test-fixture

Conversation

@leynos

@leynos leynos commented Jun 18, 2025

Copy link
Copy Markdown
Owner

Summary

  • generate unique DB names for embedded Postgres databases
  • document that PostgresTestDb uses per-test database names
  • clarify mermaid validation instructions

Testing

  • cargo clippy -- -D warnings
  • RUSTFLAGS="-D warnings" cargo test
  • cargo clippy --no-default-features --features postgres -- -D warnings (fails: could not compile postgres-setup-unpriv)
  • RUSTFLAGS="-D warnings" cargo test --no-default-features --features postgres (fails: could not compile postgres-setup-unpriv)
  • markdownlint '**/*.md'
  • nixie **/*.md

https://chatgpt.com/codex/tasks/task_e_685299d37b00832283b9fa013c62b53a

Summary by Sourcery

Generate timestamp-based unique database names for Postgres test fixtures, enable parallel-safe testing, and update related documentation and mermaid validation instructions.

New Features:

  • Generate unique per-test database names for embedded PostgreSQL fixtures to avoid naming conflicts

Enhancements:

  • Refine wording and formatting in mermaid-validation documentation for clearer instructions

Documentation:

  • Document the per-test unique database naming behavior in the rstest fixtures guide
  • Clarify Mermaid code block rendering process in the mermaid-validation guide

@sourcery-ai

sourcery-ai Bot commented Jun 18, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

Revised the Postgres test fixture to generate timestamp-based unique database names per invocation, updated mermaid validation instructions for clarity, and documented the per-test DB naming behavior in the Rust testing guide.

Class diagram for PostgresTestDb fixture changes

classDiagram
    class PostgresTestDb {
        +new() PostgresTestDb
        +db_name: String
        +connect() Connection
    }
    note for PostgresTestDb "Now generates a unique db_name per test invocation"
Loading

File-Level Changes

Change Details Files
PostgresTestDb now generates and uses unique database names for each test invocation
  • Generate db_name using current UTC timestamp via chrono
  • Pass dynamic db_name to create_database()
  • Use the new db_name when constructing the connection URL
test-util/src/lib.rs
Refined mermaid validation instructions wording
  • Merged script description into a single, continuous paragraph
  • Standardized mention of mermaid code blocks and renderer behavior
docs/mermaid-validation.md
Documented per-test unique database names in the Rust testing fixtures guide
  • Added a new '### C. Project-Specific Fixtures' section
  • Described how PostgresTestDb now prevents name conflicts in parallel tests
docs/rust-testing-with-rstest-fixtures.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jun 18, 2025

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 37 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 for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4183d41 and aa197e7.

📒 Files selected for processing (3)
  • docs/mermaid-validation.md (1 hunks)
  • docs/rust-testing-with-rstest-fixtures.md (1 hunks)
  • test-util/src/lib.rs (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch codex/use-unique-db-name-for-postgres-test-fixture

🪧 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes - here's some feedback:

  • Consider using a UUID or random suffix for the DB name to guarantee uniqueness rather than relying on the system clock, which might collide under high concurrency.
  • Ensure the test fixture cleans up/drops the created databases after each test run to avoid accumulating orphaned databases.
  • Include the generated database name in the error messages or logs to aid debugging when the fixture fails to start or create the DB.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider using a UUID or random suffix for the DB name to guarantee uniqueness rather than relying on the system clock, which might collide under high concurrency.
- Ensure the test fixture cleans up/drops the created databases after each test run to avoid accumulating orphaned databases.
- Include the generated database name in the error messages or logs to aid debugging when the fixture fails to start or create the DB.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant