Crash on MacOS 15.0.1, python 3.10.15

[tinythomasffm]

Hi,

when trying to use this action, ansible crashes on my machine:

ASK [tobias_richter.tasmota : Configure tasmota.] *****************************************************************************************************************************************************************
objc[63875]: +[NSString initialize] may have been in progress in another thread when fork() was called.
objc[63875]: +[NSString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
ERROR! A worker was found in a dead state

System is MacOS 15.0.1 with python 3.10.15 installed via homebrew.

Any ideas or hints?

Regards
Thomas

[tinythomasffm]

In case it helps:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Python [64716]
Path:                  /opt/homebrew/*/Python.framework/Versions/3.10/Resources/Python.app/Contents/MacOS/Python
Identifier:            org.python.python
Version:               3.10.15 (3.10.15)
Code Type:             ARM-64 (Native)
Parent Process:        Python [64713]
Responsible:           Terminal [1100]
User ID:               501

Date/Time:             2024-11-18 23:50:55.8486 +0100
OS Version:            macOS 15.0.1 (24A348)
Report Version:        12
Anonymous UUID:        2B6F3711-9A4C-F5C1-7100-269005B2D0D6

Sleep/Wake UUID:       513C9CFB-A48A-46A0-90DC-98B736E58797

Time Awake Since Boot: 2500000 seconds
Time Since Wake:       2173239 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace OBJC, Code 1 

Application Specific Information:
crashed on child side of fork pre-exec

[...]

[tobias-richter]

Hi, I have no mac but google reveals this ansible issue: ansible/ansible#76322

Hope that helps.

Tobias

[tinythomasffm]

Hi, thanks, that looks iike exactly my issue. Will see if that workaround does the trick. Thanks! (I actually did try to find it, but obviously lacked the right keywords to nail it down enough so google gave me a zillion results, none of them helpful…) Regards Thomas

…

Am 19.11.2024 um 07:29 schrieb Tobias Richter ***@***.***>: Hi, I have no mac but google reveals this ansible issue: ansible/ansible#76322 <ansible/ansible#76322> Hope that helps. Tobias — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASNRIPPZIRWG5BNEJWANDDL2BLLGLAVCNFSM6AAAAABSAXPNN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUHAYDQMZXGE>. You are receiving this because you authored the thread.

[tinythomasffm]

Just applied that suggested patch and it does seem to work. Thanks again for the hint!

…

Am 19.11.2024 um 07:44 schrieb Thomas Brettinger ***@***.***>: Hi, thanks, that looks iike exactly my issue. Will see if that workaround does the trick. Thanks! (I actually did try to find it, but obviously lacked the right keywords to nail it down enough so google gave me a zillion results, none of them helpful…) Regards Thomas > Am 19.11.2024 um 07:29 schrieb Tobias Richter ***@***.***>: > > > Hi, I have no mac but google reveals this ansible issue: ansible/ansible#76322 <ansible/ansible#76322> > Hope that helps. > > Tobias > > — > Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASNRIPPZIRWG5BNEJWANDDL2BLLGLAVCNFSM6AAAAABSAXPNN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUHAYDQMZXGE>. > You are receiving this because you authored the thread. >