Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ValueError: need at most 63 handles, got a sequence of length 66 #30

Closed
ohyeah521 opened this issue Aug 30, 2023 · 5 comments · Fixed by #31
Closed

ValueError: need at most 63 handles, got a sequence of length 66 #30

ohyeah521 opened this issue Aug 30, 2023 · 5 comments · Fixed by #31

Comments

@ohyeah521
Copy link

Exception in thread Thread-1:
Traceback (most recent call last):
File "C:\Python3\lib\threading.py", line 980, in _bootstrap_inner
self.run()
File "C:\Python3\lib\threading.py", line 917, in run
self._target(*self._args, **self._kwargs)
File "C:\Python3\lib\multiprocessing\pool.py", line 519, in _handle_workers
cls._wait_for_updates(current_sentinels, change_notifier)
File "C:\Python3\lib\multiprocessing\pool.py", line 499, in _wait_for_updates
wait(sentinels, timeout=timeout)
File "C:\Python3\lib\multiprocessing\connection.py", line 884, in wait
ready_handles = _exhaustive_wait(waithandle_to_obj.keys(), timeout)
File "C:\Python3\lib\multiprocessing\connection.py", line 816, in _exhaustive_wait
res = _winapi.WaitForMultipleObjects(L, False, timeout)
ValueError: need at most 63 handles, got a sequence of length 66

@ajinabraham
Copy link
Owner

Are you on latest Python?
This might be related: pycaret/pycaret#38 (comment)

@ohyeah521
Copy link
Author

ohyeah521 commented Aug 30, 2023

C:\Users>python
Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

my cpu threadripper 3975X (32 physical cores, 64 logical processors),

@ajinabraham
Copy link
Owner

64 logical processors that's it. I am trying a fix.

@ajinabraham
Copy link
Owner

I pushed a possible fix. Can you try libsast 2.0.1 and see if that fixes it?

@ohyeah521
Copy link
Author

This version of libsast 2.0.1 works properly

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 a pull request may close this issue.

2 participants