-
Notifications
You must be signed in to change notification settings - Fork 24
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
multiprocTCPBase/multiprocUDPBase not working on a Mac #92
Comments
Thespian has worked previously on Mac systems, but I haven't had a Mac for several years, so it's possible there have been changes in the OS releases in the interim. Can you provide the Mac OS release info, and also run |
|
That indicates no issues were found that the diagnostics.py were able to detect. Do any of the following work?
These should be run from the top-level checkout of the thespian repository, where the |
|
the rest work okay |
This looks like everything is in reasonable shape for the Mac and that it's primarily just a port issue for the
Let me know if one of these seems to fix the issue or if you are still having problems. |
thanks @kquick I actually checked all three several times before reporting the issue. it consistently does not work on macOS without anything else on the port. I suspect it may be one other macOS behavior that is getting in the way. I am working with docker rn to workaround this issue |
I can confirm that I have seen this as well at least for python 3.11 on MacOS Sonoma. I ended up playing around with the gatekeeper settings as I assumed there might be some odd security issue related to it ( this seemed interesting https://medium.com/@ansonliao.xiao/how-to-enable-openanywhere-security-option-in-mac-09e1570aa9ac ). I also ended up trying with python 3.9 and then installing python 3.12. In both 3.9 and 3.12 it seems like I can get thespian to launch correctly with multiprocTCPBase. Not sure if adjusting gatekeeper was the solution, but it seems to be working. |
Thank you for the update! Hopefully other Mac users can corroborate this
and we can identify the exact solution going forward.
…On Thu, Aug 8, 2024 at 10:57 PM S Kunath ***@***.***> wrote:
I can confirm that I have seen this as well at least for python 3.11 on
MacOS Sonoma. I ended up playing around with the gatekeeper settings as I
assumed there might be some odd security issue related to it ( this seemed
interesting
***@***.***/how-to-enable-openanywhere-security-option-in-mac-09e1570aa9ac
). I also ended up trying with python 3.9 and then installing python 3.12.
In both 3.9 and 3.12 it seems like I can get thespian to launch correctly
with multiprocTCPBase.
Not sure if adjusting gatekeeper was the solution, but it seems to be
working.
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGAHXI6L6UNTBJADLMBFNTZQRK6PAVCNFSM6AAAAABGSCSCMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGIYDINJRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Kevin Quick
Galois, Inc.
|
interesting. tried python 3.12 and disabling gateway without success. @skunath do you recall the exact steps you took? |
multiprocTCPBase and multiprocUDPBase fail in the same way on a Mac
tracked it down to
multiprocessCommon::_startAdmin
where the response after starting the admin comes back nullexact same setup works fine on linux, but this makes developing on a Mac difficult. triple checked nothing else is listening on the port, so not sure what is going on
startup log:
The text was updated successfully, but these errors were encountered: