-
-
Notifications
You must be signed in to change notification settings - Fork 742
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
sys.excepthook-related RuntimeWarning by trio / pyfuse3 #6352
Comments
Looks like this is an warning from Not sure where the custom Maybe it is specific to the pyinstaller-made binary (do you use the binary or how did you install borg?). You could also maybe use |
I'm also using Borgmatic. Could this be the source? |
I don't know the borgmatic details, but I guess it just calls borg as a subprocess, so there shouldn't be an influence. |
This is related to one of these, check this:
then
then again
Related python-trio/trio#1553 |
try |
I'm getting the same warning and I'm not using borgmatic, but the same Ubuntu PPA on 20.04. >>> import sys
>>> print(sys.excepthook)
<function apport_excepthook at 0x7fd7b9a39d30>
>>> So, it seems to be coming from apport/Ubuntu's Python distribution itself. Theoretically, that behavior can be reverted, just not sure where it should be added. |
Currently we just know that there is this unpretty warning. We do not know yet whether there is an actual problem or whether we prefer trio's custom handler over apport's handler. Depending on that, possible solutions:
|
Hi, Just to add my experience here. I have two Ubuntu 20.04.4 servers with the same configuration:
I only have the problem with one server. The only differences I have is regarding the packages installed via PIP. ++ EDIT: uninstalling 'pyfuse3' clear the problem, not even sure why I have it installed.... |
@jpoggi If you want |
@ThomasWaldmann ok thanks for the information, I do not use borg mount. |
This seems to be related to an outdated version of
Maybe a specific version >0.13 should be pinned. See python-trio/trio#1 |
@solracsf the first link points to an unrelated issue. although it contains the same warning, the issue is about that But as you say the warning goes away with newer trio, maybe they also have fixed something there. Requiring a specific trio version is not in scope of borgbackup though, this should be done within the https://github.com/libfuse/pyfuse3 project, so maybe file an issue there. |
I can confirm, upgrading trio to 0.20.0 does fix it |
This is happening on Ubuntu 22.10 as well, with python3-trio system package (0.21.0-1) and borg 1.22 I'm not sure when it got installed, but I don't have anything of substance that uses the library, at least nothing that installed via apt. ~ sudo apt autoremove --purge python3-trio
[sudo] password for luis:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED
python3-async-generator* python3-attr* python3-outcome* python3-pyfuse3* python3-sortedcontainers* python3-trio*
0 to upgrade, 0 to newly install, 6 to remove and 3 not to upgrade.
After this operation, 2,380 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 724924 files and directories currently installed.)
Removing python3-pyfuse3 (3.2.1-1) ...
Removing python3-trio (0.21.0-1) ...
Removing python3-async-generator (1.10-3) ...
Removing python3-outcome (1.2.0-1) ...
Removing python3-attr (22.1.0-1) ...
Removing python3-sortedcontainers (2.4.0-2) ...
~ Removing the library altogether gets rid of the warning. |
@luispabon for borg you either need If you do not use |
Thanks for the heads up 👍🏽 I don't use this feature, I personally back up to a folder within my devices then rsync into an s3 bucket afterwards which works pretty well for me. |
I confirm this using the following process on an Ubuntu 20.04 LTS:
|
Guess this should be fixed in more recent Ubuntu releases. And anyway: it is not a borg bug, thus I am closing this here. |
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes, searched for "RuntimeWarning", no similar results
Is this a BUG / ISSUE report or a QUESTION?
Bug
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.0 + Python 3.8.10
Operating system (distribution) and version.
Ubuntu 20.04.3
Full borg commandline that lead to the problem (leave away excludes and passwords)
The text was updated successfully, but these errors were encountered: