From: pascal-huber <pascal-huber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] offlineimap: sqlite multithreading error
Date: Thu, 10 Nov 2022 01:21:44 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40425@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
New issue by pascal-huber on void-packages repository
https://github.com/void-linux/void-packages/issues/40425
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.17_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFFF
### Package(s) Affected
offlineimap-8.0.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
issue: https://github.com/OfflineIMAP/offlineimap3/issues/136
PR: https://github.com/OfflineIMAP/offlineimap3/pull/137
### Expected behaviour
`offlineimap` syncs mails.
### Actual behaviour
offlineimap throws errors of the form:
```
Your sqlite is not multithreading safe.
Folder someFolder [acc: MyAccount]:
ERROR: ERROR in syncfolder for MyAccount folder tempKeep: Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/offlineimap/accounts.py", line 610, in syncfolder
statusfolder.openfiles()
File "/usr/lib/python3.11/site-packages/offlineimap/folder/LocalStatusSQLite.py", line 107, in openfiles
assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.'
AssertionError: Your sqlite is not multithreading safe.
```
### Steps to reproduce
1. Add an `.offlineimaprc` config containing a mail account
2. run `offlineimap`
next reply other threads:[~2022-11-10 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 0:21 pascal-huber [this message]
2022-11-10 0:25 ` pascal-huber
2022-11-10 0:52 ` [ISSUE] [CLOSED] offlineimap: python 3.11 " sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40425@inbox.vuxu.org \
--to=pascal-huber@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).