Skip to content

Omri/nom 8044 litellm noma v2 fix deepcopy crash in build scan payload - #8

Open
omriShukrun08 wants to merge 7 commits into
mainfrom
omri/NOM-8044-Litellm-Noma-v2-fix-deepcopy-crash-in-_build_scan_payload
Open

Omri/nom 8044 litellm noma v2 fix deepcopy crash in build scan payload#8
omriShukrun08 wants to merge 7 commits into
mainfrom
omri/NOM-8044-Litellm-Noma-v2-fix-deepcopy-crash-in-_build_scan_payload

Conversation

@omriShukrun08

@omriShukrun08 omriShukrun08 commented Apr 18, 2026

Copy link
Copy Markdown

Relevant issues

Noma v2 integration experiences a 500 error during post_call/during_call/during_mcp_call due to deepcopy(request_data) failing on unserializable objects (uvloop.Loop) in _build_scan_payload. A JSON-safe copy method is needed, similar to the approach in spend_tracking_utils.py and its _sanitize_payload_for_transport() helper, which currently runs after the deepcopy crash.

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.
  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Screenshots / Proof of Fix

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

@omriShukrun08 omriShukrun08 reopened this Apr 18, 2026
TomAlon pushed a commit that referenced this pull request Apr 26, 2026
Audit-B #7 and #8.

1. /organization/member_delete was not in org_admin_only_routes, so it
   fell through to management_routes/self_managed_routes and let any
   caller that reached the route delete arbitrary org memberships
   without the organization_role_based_access_check that member_add
   and member_update trigger. Adding it to org_admin_only_routes
   applies the same ORG_ADMIN-of-target-org gate.

2. /organization/member_update had no validation that the target user
   was not a global PROXY_ADMIN. An org-admin of any org could alter
   a PROXY_ADMIN user's per-org role. Reject this unless the caller
   is PROXY_ADMIN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants