-
Notifications
You must be signed in to change notification settings - Fork 193
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
Cannot recover using python >=3.8 on macOS #838
Comments
For completeness I should note that the Barman project is developed primarily for Linux systems and we do not support macOS. |
Came across the following links. I taught it might help to resolve the issue. The possible root cause of the issue: And maybe a solution can be found here: |
Info in the light of the upcoming python 3.12 release: Look for multiprocessing in https://docs.python.org/3.12/whatsnew/3.12.html |
@ARCICT Thanks for looking into this - I think you are correct about the possible root cause, given the recovery code uses multiprocessing.Pool.imap_unordered to spawn copy jobs, and that the issue only affects macOS on Python versions >= 3.8. For confirmation I tried setting We'll need a bit of time to figure out the best solution and, going by the Python 3.12 release notes (thanks again for the heads-up about that one), it looks like we're going to need to solve it if we want Barman to continue working under Linux on Python 12 and later. |
Mike,
|
Hi @ARCICT - I added a
I'm hesitant to propose this as the long term solution because of the comments about the safety of |
@mike, Regarding the good longterm solution we are looking at the python wizards :-) |
@gcalacoci Guilio, Works like a charm ! |
Recovery currently fails when running Barman on Python 3.11 on macOS.
Originally reported on the mailing list and reproducible by creating a python 3.11 virtualenv and attempting to recover a backup:
This is not an issue using earlier versions of python on macOS and it also does not appear to be an issue with python 3.11 on non macOS systems.
Update: After further testing this is an issue all the way back to python 3.8 on macOS.
The text was updated successfully, but these errors were encountered: