s3ql 3.7.0 crash, version bump requested

Bug #1928030 reported by Henry Wertz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
s3ql (Ubuntu)
New
Undecided
Unassigned

Bug Description

I "backported" s3ql (built .debs for python3-pyfuse3_3.2.0-2build1, python3-trio_0.18.0-1, and s3ql_3.7.0+dfsg-2build1-local1 to use in Ubuntu 20.04), and encountered a fairly quick crash (like under a minute) when I started writing data to the s3ql filesystem. The log ends with several "During handling of the above exception, another exception occurred:" python tracebacks, ending with "s3ql.block_cache.NoWorkerThreads: no upload threads". Per the bug referenced, this won't result in data loss, a umount + fsck.s3ql cleans it up fine. But still.

https://github.com/s3ql/s3ql/issues/234

Bug fixed in 3.7.1, I built 3.7.2 and it works a treat. No crashes under very heavy usage; it's a bit faster than 3.3.4 that 20.04 focal ships with in general usage and much faster to unmount.

3.7.0 is current version in hirsute and impish, so should be bumped to 3.7.2.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.