Commit Graph

9 Commits

Author SHA1 Message Date
eta 14ff49b1d2 sqlite: attempted fix for persistent MISUSE errors
- Sometimes, the bridge can get wedged in a state where doing DB operations
  returns SQLITE_MISUSE errors.
- I don't really know what causes this, but I'm hoping unconditionally resetting
  the statements before they get used will ameliorate the problem?
- Additionally, the reset statements now aren't wrapped in an IGNORE-ERRORS,
  meaning we might get error tracebacks that point to the actual problem now.
2020-09-16 13:06:52 +01:00
eta 39001728b3 slightly hacky but functional groupchat / MUC support 2020-04-12 08:27:04 +01:00
eta 2f4e78bc8c Revert "hold my beer, let's remove *DB-LOCK*"
This reverts commit f6561a64a3.
2020-04-06 21:24:16 +01:00
eta f6561a64a3 hold my beer, let's remove *DB-LOCK*
- We shouldn't need it anyway because of the component data lock, and having two
  locks around causes deadlocks (they're taken in different orders)
2020-04-06 20:31:59 +01:00
eta 47024701a5 Handle avatars (!) and various types of presence requests 2020-04-05 15:05:27 +01:00
eta 12cb121100 Handle presence subscriptions, vcard-temp, and other stuff 2020-04-04 23:12:39 +01:00
eta e2add1d98f Actually reconnect users & connect on bridge start 2020-04-04 17:18:26 +01:00
eta 5c9a257f5c It actually connects to WhatsApp! Who'd have thought it? 2020-04-04 15:24:51 +01:00
eta 2d873df755 IQ handlers, XEP-0363 stuff, and SQLite, oh my! 2020-04-03 17:40:05 +01:00