fix(profile): validate username uniqueness before profile updates#674
Merged
param20h merged 1 commit intoJun 23, 2026
Merged
Conversation
param20h
approved these changes
Jun 23, 2026
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
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.
📋 PR Checklist
🔗 Related Issue
Closes #673
📝 What does this PR do?
This PR fixes a bug in the
PUT /profileendpoint where username updates bypassed application-level uniqueness validation.Previously, if a user attempted to change their username to one already used by another account, the database unique constraint would trigger an unhandled
IntegrityError, resulting in a500 Internal Server Error.Changes made:
IntegrityErrorhandling with transaction rollback to safely handle race conditions.🗂️ Type of Change
🧪 How was this tested?
uvicorn app.main:app --reload)npm run devinsidefrontend/)Validation Performed
Added regression tests for:
Executed:
Executed full backend test suite:
📸 Screenshots (if UI change)
N/A (Backend-only change)
IntegrityErrorhandling to protect against concurrent update race conditions.✅ Self-Review Checklist
dev, notmainmainbranch or any HuggingFace deployment config