AMOOOMA commented on code in PR #37112:
URL: https://github.com/apache/beam/pull/37112#discussion_r2710130964


##########
sdks/python/apache_beam/utils/multi_process_shared.py:
##########
@@ -200,9 +226,99 @@ def __call__(self, *args, **kwargs):
   def __getattr__(self, name):
     return getattr(self._proxyObject, name)
 
+  def __setstate__(self, state):
+    self.__dict__.update(state)
+
+  def __getstate__(self):
+    return self.__dict__

Review Comment:
   Just tried removing these and run the test locally, it's this infinite 
recursion thing that will happen if i have a proxy on a proxy 
   
   ```
   <string>:2: in make_proxy
       ???
   
../../../../.pyenv/versions/3.11.14/lib/python3.11/multiprocessing/managers.py:822:
 in _callmethod
       kind, result = conn.recv()
                      ^^^^^^^^^^^
   
../../../../.pyenv/versions/3.11.14/lib/python3.11/multiprocessing/connection.py:251:
 in recv
       return _ForkingPickler.loads(buf.getbuffer())
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   apache_beam/utils/multi_process_shared.py:226: in __getattr__
       return getattr(self._proxyObject, name)
                      ^^^^^^^^^^^^^^^^^
   apache_beam/utils/multi_process_shared.py:226: in __getattr__
       return getattr(self._proxyObject, name)
                      ^^^^^^^^^^^^^^^^^
   apache_beam/utils/multi_process_shared.py:226: in __getattr__
       return getattr(self._proxyObject, name)
                      ^^^^^^^^^^^^^^^^^
   E   RecursionError: maximum recursion depth exceeded
   !!! Recursion detected (same locals & position)
   ```



##########
sdks/python/apache_beam/utils/multi_process_shared.py:
##########
@@ -79,6 +83,10 @@ def singletonProxy_release(self):
     assert self._SingletonProxy_valid
     self._SingletonProxy_valid = False
 
+  def unsafe_hard_delete(self):

Review Comment:
   Sg! Updated.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to