Conversation
feat: add Redis/Kafka boilerplate for distributed environment migration
…-QuizPlatform/MoMoGo into feature/jwtRegistry-redis
…edis feat: impl RedisJwtRegistry
…eviews for realtime websocket
… RedisMessagerPublisher
…s-pubsub Feat: impl STOMP Websocket Redis pub/sub message relay with DTO and constants
feat: configure AWS S3 storage integration and env properties
… Redis config - Replace local Spring event with AiGradingProducer message publishing in RoomServiceImpl - Convert AiGradingEventListener to @KafkaListener async consumer to eliminate CPU bottleneck and blocking - Add KafkaTopics.AI_GRADING_EVENTS constant and AiGradingEventDto - Explicitly declare LettuceConnectionFactory bean in RedisConfig to resolve Redisson StackOverflowError - Add default environment placeholders in application.yaml and S3StorageService for local setup
…is config - Re-throw exceptions in AiGradingEventListener to activate global Kafka retry & DLT policy - Add immutable UUID eventId to AiGradingEventDto for message idempotency - Add whenComplete callback in AiGradingProducer for async delivery tracking - Bind Spring Boot RedisProperties in RedisConfig to support database/timeout properties
TTL 만료 후 다른 요청이 같은 키로 락을 재획득했을 때, 기존 요청의 실패 처리가 무조건 delete를 호출해 새 락을 지우는 문제가 있었음. 락 값을 요청별 토큰으로 바꾸고 Lua compare-and-delete로 소유자만 해제하도록 수정. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
catch(RuntimeException)만 처리해 성공 시 락이 TTL까지 남고, Error 계열(OOM 등) 발생 시 락 누수가 있었음. finally로 바꿔 성공/실패/Error 모든 경로에서 락이 해제되도록 수정. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
feat: add Idempotency-Key guard to prevent duplicate AI problem generation
deleteRoomProblem read the room without acquiring a lock, then bulk- updated problemOrder before deleting the target row. Concurrent delete requests on the same room could race and leave problemOrder with gaps or an inconsistent sequence, more likely across multiple instances. Switch to roomRepository.findByIdForUpdate, the same pessimistic-lock pattern already used by createRoomProblemsByAi via RoomProblemPersister#saveGeneratedProblems, so concurrent deletes on the same room are serialized. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…m-problem creation Both createCategory (name uniqueness) and createRoomProblem (problem order uniqueness) only guarded against duplicates with a pre-check (existsByName / relying on the DB constraint alone). Under concurrent requests the pre-check can pass for both callers, leaving the DB unique constraint as the only real guard, which surfaced as an unmapped DataIntegrityViolationException instead of the intended BusinessException. Wrap the save in saveAndFlush + catch DataIntegrityViolationException, matching the existing isDuplicateEmailViolation pattern in UserServiceImpl: inspect getMostSpecificCause().getMessage() for the constraint name and rethrow as a BusinessException, otherwise propagate. Added RoomProblemErrorCode.DUPLICATE_PROBLEM_ORDER (7005); reused the existing CATEGORY_NAME_DUPLICATED for categories. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
fix: lock room row before reordering on problem deletion
Feat: Setup Spring Boot Actuator with Prometheus and Grafana monitoring
… into feature/login-refactor # Conflicts: # momogo-core/build.gradle
feat: impl BoundedBCryptPasswordEncoder and Redis cache configuration
…all spaces Add force update/delete for spaces and full CRUD for problems that bypass per-space ADMIN ownership checks, scoped to SUPER_ADMIN only.
…firm Remove the mock interceptor for /api/super-admin/spaces and /problems so the console hits the real API, paginate through all results, and drop the now-stale demo-data banners. Add the notification bell to the space problem-bank page, surface confirm failures as a toast instead of only logging them, and filter already-confirmed notifications out of the list so confirmed items don't reappear.
Connect the SSE stream first and only fetch GET /api/notifications after the server's connect event is received, so notifications created between the list fetch and the SSE connection are no longer lost. connectNotificationSse now exposes the connect event's id via an onConnect callback.
feat: 슈퍼관리자 콘솔 백엔드 연동 및 알림 확인 버그 수정
refactor: change deploy
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (94)
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
작업 내용
Develop to Main Ver.3
변경 사항
체크리스트
참고 사항
관련 이슈