Re: Duplicity ResourceWarning: unclosed file

Hello Xavier,

I'm running duplicity on amd64 main with no problems (backup and checked
--version).

I don't have access to amd64 logs right now but it builds fine without
issues on my arm64 rpi4:
http://freebsdrpi4.hopto.org/data/15aarch64-main/2024-07-12_12h32m44s/logs/duplicity-3.0.0.log

I will check amd64 logs when I've got the chance.

Thanks,

Xavier Humbert <xavier@groumpf.org> escreveu (domingo, 14/07/2024 à(s)
09:11):

> Hi,
>
> Since the last upgrade of Duplicity, I experience these warnings :
>
>
> =====================================================================================
> /usr/local/lib/python3.11/threading.py:986: ResourceWarning: unclosed
> file <_io.BufferedReader name=5>
>    del self._target, self._args, self._kwargs
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/local/lib/python3.11/site-packages/duplicity/backends/ssh_paramiko_backend.py:461:
>
> ResourceWarning: unclosed file <_io.TextIOWrapper
> name='/etc/ssh/ssh_config' mode='r' encoding='UTF-8'>
>    sshconfig.parse(open(file))
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Mon Jul  1 10:33:46 2024
> /usr/local/lib/python3.11/site-packages/duplicity/dup_main.py:779:
> ResourceWarning: unclosed file <_io.BufferedReader
>
> name=b'/root/.cache/duplicity/b0ba93458b58f009d3339ea64701a6b2/duplicity-inc.20240714T020354Z.to.20240714T075149Z.manifest.part'>
>    new_man_outfp.to_remote()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/local/lib/python3.11/site-packages/duplicity/dup_main.py:780:
> ResourceWarning: unclosed file <_io.BufferedReader
>
> name=b'/root/.cache/duplicity/b0ba93458b58f009d3339ea64701a6b2/duplicity-inc.20240714T020354Z.to.20240714T075149Z.manifest.part'>
>    new_man_outfp.to_final()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
>
> =====================================================================================
>
> A similar issue has been reported in 2019 :
> https://bugs.launchpad.net/duplicity/+bug/1847122
>
> The warning appears also when I ask for Duplicity version :
>
>
> =====================================================================================
> duplicity 3.0.0 May 29, 2024
> /usr/local/lib/python3.11/threading.py:986: ResourceWarning: unclosed
> file <_io.BufferedReader name=5>
>    del self._target, self._args, self._kwargs
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
>
> =====================================================================================
>
> Again in rebuild of duplicity, same warning
>
>
> =====================================================================================
> ===>   duplicity-3.0.0 depends on package: py311-future>0 - found
> ===>   duplicity-3.0.0 depends on package: py311-mock>0 - found
> ===>   duplicity-3.0.0 depends on package: py311-paramiko>=0 - found
> ===>   duplicity-3.0.0 depends on package: py311-pexpect>0 - found
> ===>   duplicity-3.0.0 depends on package: py311-requests>=0 - found
> ===>   duplicity-3.0.0 depends on package: py311-urllib3>=0 - found
> ===>   duplicity-3.0.0 depends on package: py311-b2sdk>=0.1.8 - found
> ===>   duplicity-3.0.0 depends on package: py311-dropbox>0 - found
> ===>   duplicity-3.0.0 depends on package: gnupg1>=1.4.7 - found
> ===>   duplicity-3.0.0 depends on file: /usr/local/bin/python3.11 - found
> ===>   Generating temporary packing list
> sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper
> name='/usr/ports/sysutils/duplicity/work/stage/usr/local/lib/python3.11/site-packages/duplicity-3.0.0.dist-info/RECORD'
>
> mode='r' encoding='utf-8'>
>
> =====================================================================================
>
> Should I report upstream ?
>
> Regards,
>
> Xavier
>
> --
> Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
> https://www.amdh.fr
>
>
>

-- 
Nuno Teixeira
FreeBSD UNIX:  <eduardo@FreeBSD.org>   Web:  https://FreeBSD.org