Backend: Database session is not rolled back when user/org creation fails

[charu2210]

Description

When create_user() or create_organization() fails during await self.db_session.commit() in backend/app/utils/jwt_auth.py, the exception is re-raised without calling await self.db_session.rollback().

This leaves the SQLAlchemy session in a failed transaction state, which can cause later DB operations to fail with PendingRollbackError.

Steps to Reproduce

1. Trigger a DB commit failure during signup/org creation
2. Attempt another DB operation using the same session
3. Observe transaction/session errors

Expected Behavior

The DB session should be rolled back after a failed commit.

Actual Behavior

The session remains in an invalid transaction state.

Suggested Fix

Add rollback handling inside the exception blocks:

except Exception:
    await self.db_session.rollback()
    raise

Environment

• Backend
• FastAPI
• SQLAlchemy AsyncSession

[github-actions]

👋 Hey @charu2210, thanks for raising this issue!

A maintainer will review it shortly. If you'd like to work on a fix, please read the guidelines below before opening a PR.

---

📋 Before You Start

Look at our merged pull requests to understand the expected commit style and code quality before writing a single line.

Merged PRs are the best source of truth for:

• How commits should be worded and structured
• How code is organised (file structure, naming, patterns)
• What a clean, reviewable PR looks like

---

✅ Clean Commit History — Required

We follow Conventional Commits:

Prefix	Use for
feat:	New feature
fix:	Bug fix
chore:	Tooling / config / deps
docs:	Documentation only
refactor:	Code restructuring (no behaviour change)
test:	Adding or fixing tests

Branch naming: feat/<short-description> or fix/<short-description>

Rules:

• 🚫 No force-push to main or shared branches
• 🚫 No merge commits inside your feature branch — rebase instead
• ✅ One logical change per commit
• ✅ PR must reference this issue: Closes #136

---

Happy contributing! 🚀

[charu2210]

/assign
I would like to work on this issue under gssoc.

[ShreeniG99]

@sathwikshetty33
I'd like to fix this. I'm Shreenidhi, a GSSoC'26 contributor.
When user or org creation fails mid-transaction, the session needs an explicit session.rollback() in the exception handler ... otherwise the session stays in a broken state and future requests on that connection will fail. I'll wrap the creation logic in a proper try/except/finally block with a rollback on failure.
Can u pls assign this to me?