acme/platform#4821/3

coderabbitaibotreviewed 2m ago

Invalidate the cache after the mutation.

The record updates, but the stale project key remains in Redis.

- await db.project.update(input)

+ await updateProjectAndInvalidate(input)

codexcoding agentreplied 1m ago

Fixed in 9f2c4a1 — invalidation now runs after the transaction, with a regression test for the stale-cache path.

coderabbitaibotchecked now

Verified. The cache is cleared after commit and the new test covers the failure mode.

coderabbitaibotreviewed 3m ago

Return the HTTP error from the service layer.

This keeps the handler smaller and centralizes error mapping.

shaun-kauthorreplied 2m ago

@coderabbitai In this repository, handlers own the HTTP mapping. Services return domain errors.

coderabbitaibotreplied now

Understood — I'll follow that convention in future reviews.

New Learnings Added

User: shaun-k

PR: acme/platform#482

File: app/api/projects/route.ts:42–58

Learning: Handlers map domain errors to HTTP responses.

coderabbitaibotupdated just now

Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	Passed	The PR description follows the repository template.
Title Check	Passed	The title clearly describes the payment-limit change.
Docstring Coverage	Passed	No changed functions require docstrings.

🚀 Post-Merge Actions

Update changelog
Notify release channel
Sync docs

coderabbitaibotcommented just now

🚀 Post-Merge Actions

@shaun-k, one or more post-merge actions failed.

Update changelog — opened follow-up PR #483
Notify release channel — Slack connection unavailable.

coderabbitaibotreviewed 2m ago

Invalidate the cache after the mutation.

The record updates, but the stale project key remains in Redis.

- await db.project.update(input)

+ await updateProjectAndInvalidate(input)

codexcoding agentreplied 1m ago

Fixed in 9f2c4a1 — invalidation now runs after the transaction, with a regression test for the stale-cache path.

coderabbitaibotchecked now

Verified. The cache is cleared after commit and the new test covers the failure mode.

Code reviews built for agent-driven development.

Get instant, context-aware feedback on every commit.

Get started freeReview in the CLI

Available for

GitHub

GitLab

Your automated first line of defense.

Teams are drowning in massive pull requests. Let AI do the heavy lifting with a line-by-line inspection of every change.

Correctness and tests. Inspect behavior, edge cases, and test coverage before a person starts reviewing.

Security and policy. Challenge risky changes against security expectations and team rules.

Consistency and completeness. Catch unfinished work, mismatched patterns, and missing follow-through across the pull request.

A purpose-built harness for independent review.

A purpose-built harness routes review work across multiple models and verification agents before comments are posted.

Context agent
Call path analysis
Review agent
Mutation analysis
Security agent
Sandbox scenario

Industry-leading context

Bring in repository context, relationships, and team guidance for reviews that understand your codebase.

Code Graph

Build a semantic map of your repositories, relationships, dependencies, and blast radius.

Sandbox evidence

Reproduce suspected failure modes in a sandbox to add evidence to selected findings.

Learning as a compounding loop

Capture useful corrections as Learnings that can inform future reviews and carry approved team standards forward.

CodexClaude

Add reviews to your agent loop.

Coding agents apply fixes, then developers can rerun review before a change reaches a human reviewer.

acme/platform#4821/3

coderabbitaibotreviewed 2m ago

Invalidate the cache after the mutation.

The record updates, but the stale project key remains in Redis.

- await db.project.update(input)

+ await updateProjectAndInvalidate(input)

codexcoding agentreplied 1m ago

Fixed in 9f2c4a1 — invalidation now runs after the transaction, with a regression test for the stale-cache path.

coderabbitaibotchecked now

Verified. The cache is cleared after commit and the new test covers the failure mode.

coderabbitaibotreviewed 3m ago

Return the HTTP error from the service layer.

This keeps the handler smaller and centralizes error mapping.

shaun-kauthorreplied 2m ago

@coderabbitai In this repository, handlers own the HTTP mapping. Services return domain errors.

coderabbitaibotreplied now

Understood — I'll follow that convention in future reviews.

New Learnings Added

User: shaun-k

PR: acme/platform#482

File: app/api/projects/route.ts:42–58

Learning: Handlers map domain errors to HTTP responses.

coderabbitaibotupdated just now

Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	Passed	The PR description follows the repository template.
Title Check	Passed	The title clearly describes the payment-limit change.
Docstring Coverage	Passed	No changed functions require docstrings.

🚀 Post-Merge Actions

Update changelog
Notify release channel
Sync docs

coderabbitaibotcommented just now

🚀 Post-Merge Actions

@shaun-k, one or more post-merge actions failed.

Update changelog — opened follow-up PR #483
Notify release channel — Slack connection unavailable.

coderabbitaibotreviewed 2m ago

Invalidate the cache after the mutation.

The record updates, but the stale project key remains in Redis.

- await db.project.update(input)

+ await updateProjectAndInvalidate(input)

codexcoding agentreplied 1m ago

Fixed in 9f2c4a1 — invalidation now runs after the transaction, with a regression test for the stale-cache path.

coderabbitaibotchecked now

Verified. The cache is cleared after commit and the new test covers the failure mode.

Automate the manual work around the merge.

Keep pull requests moving without turning every routine task into another handoff.

Instant fixes

Address every review comment in one click or generate a new pull request.

Pre-Merge Checks

Automate manual pull request checklists with built-in and custom checks.

Finishing Touches

Add unit tests and docstrings, resolve merge conflicts, simplify code, or split a large pull request into smaller change sets.

Post-Merge Actions

Create changelog entries, update docs, file tickets, post Slack summaries, open cleanup pull requests, and more.

Reviews across every surface.

Review in your IDE and CLI while context is fresh, then review again in your Git provider.

IDE

Review before you commit

CLI

Keep the agent loop moving

Git provider

Review the complete pull request

Why CodeRabbit over your coding agent?

Keep the system that writes code separate from the system that decides whether it is ready to ship.

Central

One code review layer, no matter how many agents your team uses.

Independent

Coding agents are optimized to write code. CodeRabbit is optimized to challenge it.

Team-wide

One source of reviews and team standards for every author, reviewer, and agent.

Agentic Change Management for every change.

Validate, prioritize, understand, and secure every change.

Validate

Review

Prioritize

Triage

Understand

Change Stack

Secure

Security

Put an independent review layer
on every change.

Start reviewing with CodeRabbit today.

Get started free Book a demo