Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py
I believe s3ql 3.8.0 just released, and it now states it requires trio >= 0.15. https://github.com/s3ql/s3ql/commit/105dd0d62670570cd0e77cf9cbfa967f7f4130fe Although, that's just the documentation I think. Actual "requirement" was set here: https://github.com/s3ql/s3ql/commit/7c955eda5d058dcbf59c7c63066fcccdbac13494#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7 On Wed, 17 Mar 2021 at 03:54, Andrey Rahmatullin wrote: > On Thu, Feb 18, 2021 at 03:28:36PM +0100, Francesco P. Lovergine wrote: > > I'm pretty sure this release should depend on >= 0.15, > > even due to #981906. Unfortunately, it is not expressed in the package > From setup.py: > > # Need trio.lowlevel > 'trio >= 0.15', > > So it's expressed upstream but ignored in the Debian package, because > dh_python3 ignores version reqs by default. > > > -- > WBR, wRAR >
Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py
On Thu, Feb 18, 2021 at 03:28:36PM +0100, Francesco P. Lovergine wrote: > I'm pretty sure this release should depend on >= 0.15, > even due to #981906. Unfortunately, it is not expressed in the package From setup.py: # Need trio.lowlevel 'trio >= 0.15', So it's expressed upstream but ignored in the Debian package, because dh_python3 ignores version reqs by default. -- WBR, wRAR signature.asc Description: PGP signature
Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py
On Sun, Feb 14, 2021 at 01:38:58PM +1100, Lorentz Kim wrote: Hi, I don't know if it'll help much, but I've also gotten this bug and have resolved it by manually upgrading python3-trio with pip to its latest version, overriding system's installed version (which is 0.13 last I checked). pip install trio==0.18.0 Pretty sure the s3ql release notes for 3.7 suggests anything after trio 0.9 is supported, but perhaps there's a bug in there somewhere? Regards, Lorentz I'm pretty sure this release should depend on >= 0.15, even due to #981906. Unfortunately, it is not expressed in the package, so yes it is an upstream issue apparently. -- Francesco P. Lovergine
Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py
Hi, I don't know if it'll help much, but I've also gotten this bug and have resolved it by manually upgrading python3-trio with pip to its latest version, overriding system's installed version (which is 0.13 last I checked). pip install trio==0.18.0 Pretty sure the s3ql release notes for 3.7 suggests anything after trio 0.9 is supported, but perhaps there's a bug in there somewhere? Regards, Lorentz
Bug#982381: AttributeError: lowlevel due to trio usage in s3ql/block_cache.py
Package: s3ql
Version: 3.7.0+dfsg-2
Severity: important
Dear Maintainer,
mount.s3ql is generating the following error:
$ mount.s3ql --systemd --log none --fg s3://.../ "..."
<6>Using 10 upload threads.
<6>Autodetected 1048514 file descriptors available for cache entries
<6>Using cached metadata.
<6>Setting cache size to 6040 MB
<6>Loaded 0 entries from cache
<3>Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/bin/mount.s3ql", line 33, in
sys.exit(load_entry_point('s3ql==3.7.0', 'console_scripts', 'mount.s3ql')())
File "/usr/lib/s3ql/s3ql/mount.py", line 131, in main
trio.run(main_async, options, stdout_log_handler)
File "/usr/lib/python3/dist-packages/trio/_core/_run.py", line 1804, in run
raise runner.main_task_outcome.error
File "/usr/lib/s3ql/s3ql/mount.py", line 207, in main_async
block_cache.init(options.threads)
File "/usr/lib/s3ql/s3ql/block_cache.py", line 222, in init
self.trio_token = trio.lowlevel.current_trio_token()
File "/usr/lib/python3/dist-packages/trio/_deprecate.py", line 125, in
__getattr__
raise AttributeError(name)
AttributeError: lowlevel
This happens 100% of the time
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (520, 'testing'), (510, 'stable'), (150, 'unstable'), (120,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages s3ql depends on:
ii fuse3 [fuse] 3.10.1-3
ii libc6 2.31-9
ii libjs-sphinxdoc 3.4.3-1
ii libsqlite3-0 3.34.1-1
ii procps2:3.3.16-5
ii psmisc23.3-1
ii python3 3.9.1-1
ii python3-apsw 3.32.2-r1-1+b2
ii python3-cryptography 3.3.1-1
ii python3-defusedxml0.6.0-2
ii python3-dugong3.8.1+dfsg-1
ii python3-google-auth 1.5.1-3
ii python3-google-auth-oauthlib 0.4.2-1
ii python3-pkg-resources 51.3.3-1
ii python3-pyfuse3 3.2.0-1+b1
ii python3-requests 2.25.1+dfsg-2
ii python3-systemd 234-3+b4
ii python3-trio 0.13.0-2
s3ql recommends no packages.
s3ql suggests no packages.
-- no debconf information
