Conversation
- Upgrade waku from 1.0.0-alpha.6 to 1.0.0-alpha.7 (Vite 8 official support) - Remove vite/plugin-react overrides (no longer needed with alpha.7) - Clean up workaround comment in waku.config.ts
Custom emojis were rendered too small due to cva default size="md"
(h-10 px-4 py-2) overriding the className padding. Pass size={null}
to all emoji buttons and use w-7 h-7 for custom emoji images.
Replace scroll-to-bottom pagination with per-category IntersectionObserver sentinels. Emojis now load seamlessly as the user scrolls within each accordion section, instead of requiring the modal to reach the bottom.
Use Symbol.for-based global singleton to prevent dual-instance issues when the module is loaded via different resolution paths (CJS/ESM). Also remove .js extension from test import.
The mock.module for NotificationStreamService was leaking to other test files in Bun 1.3.12. Provide a complete mock with all public methods and remove .js extension from mock path to match imports.
- Remove mock.module for NotificationStreamService (caused leakage across test files in Bun 1.3.12 on Linux) - Revert unnecessary Symbol.for singleton workaround - Upgrade actions/checkout v4 -> v6, actions/setup-node v4 -> v6 to resolve Node.js 20 deprecation warnings
… components - shared: Add TSDoc to all exported types, interfaces, and validation constants - backend: Replace Japanese comments with English TSDoc in IFileStorage, IUserRepository, di middleware, and OAuth routes - frontend: Add @returns to SpinnerWithLabel
404 responses during OGP fetch are expected (e.g. deleted users/notes, crawlers with bad URLs). Remove console.error to avoid polluting production logs with stack traces for non-error conditions.
JSON logs are hard to read in journalctl. Enable pino-pretty in all environments (colorize disabled in production to avoid ANSI codes). Set LOG_PRETTY=false to opt out if JSON is preferred.
The plugins directory is optional. ENOENT when it doesn't exist is expected behavior, not an error condition.
chore: bump version to 2026.4.1
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 22 minutes and 35 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (30)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Test plan