fix(langfuse): replace MagicMock with Mock to prevent RAM exhaustion (#2543) #2798
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.
Fixes bug(langfuse): test_create_new_span causes excessive RAM usage and hangs due to unspecced MagicMock #2543
test hangs on Linux Python 3.9/3.13 due to unspecced
MagicMock().Changes
Replaced
MagicMock()withMock()on lines571and589intest_tracer.py.Unspecced
MagicMockcreates infinite child mocks on attribute access, which causedhandle()to hang while iterating mock objects. A partial workaround existed (get_data.return_value = {}), but the root mocks were still unspecced.Testing
test_create_new_spanpassesNote
Two pre-existing failures (
test_set_content_tag_updates_input_and_output*) exist onmainand are unrelated; should be tracked separately.