fix: unwrap MutableProxy values in _mark_dirty before writing

[benedikt-bartscher]

No description provided.

[codspeed-hq]

Merging this PR will degrade performance by 3.02%

❌ 1 regressed benchmark
✅ 7 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	test_compile_stateful[_stateful_page]	150.8 µs	155.5 µs	-3.02%

---

_{Comparing benedikt-bartscher:sqla-mutable-proxy (18488dd) with main (e7c3742)}

[greptile-apps]

Greptile Summary

Fixed a bug where MutableProxy objects were leaking into underlying data structures when performing mutation operations (append, extend, insert, setitem, setattr). The proxies are designed as read-path wrappers and should not persist in the actual stored data.

The fix adds a new static method _unwrap_proxy_arg that recursively unwraps proxy objects from values before writing them. This method handles:

• Direct proxy instances
• Lists, tuples, and sets containing proxies
• Dict keys and values that are proxies
• Scalar values (pass-through unchanged)

The unwrapping is applied in _mark_dirty before calling the wrapped mutation function, ensuring that only raw objects are written to the underlying data structures while preserving dirty tracking functionality.

Testing:

• Extensive test coverage added for all affected mutation operations
• Tests verify that proxies don't leak into underlying structures
• Tests confirm object identity is preserved after unwrapping
• Tests ensure dirty tracking still works correctly after the fix

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is well-designed and addresses a clear bug with proxy leakage. The implementation is clean, handles all common container types appropriately, and includes comprehensive test coverage (11 new tests). All tests verify both the fix and that existing functionality (dirty tracking) remains intact. No edge cases or potential issues identified.
• No files require special attention

Important Files Changed

Filename	Overview
reflex/istate/proxy.py	Added _unwrap_proxy_arg method to prevent MutableProxy objects from leaking into underlying data structures during mutations
tests/units/istate/test_proxy.py	Added comprehensive test coverage for proxy unwrapping across various mutation operations (append, extend, insert, setitem, setattr)

_{Last reviewed commit: 18488dd}

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[masenf]

@benedikt-bartscher what is the use case / bug fixed by this patch? Is there a problem if the data structures get proxy objects added to them? When serializing to redis, we don't serialize the proxy objects, so they get refreshed each time the state is reloaded for processing another event.

Also noticed that if the args is a mutable proxy of a list that contains other mutable proxy as items, then these items will not be unwrapped, not sure if that was intentional or not.

[benedikt-bartscher]

@masenf MutableProxy caused issues with sqlalchemy realtions. If i have spare time for it, i may add a unit test with sqlalchemy