d3c9de4712
Add debug module
...
Lets us generate large conversations with large attachments.
7 years ago
30037e5308
Reduce attachment migration batch size to 1
...
This prevents ‘Maximum IPC message size exceeded’ due to IDB `getAll` operation.
- https://github.com/zincbase/zincdb/issues/17
- https://cs.chromium.org/chromium/src/content/browser/indexed_db/indexed_db_database.cc?q=%22Maximum+IPC+message+size+exceeded%22&sq=package:chromium&l=1160
7 years ago
ce8fd3d847
Expose `Signal.Settings` module
7 years ago
02354ce655
Expose `Signal.Database` module
7 years ago
21147a20a0
Add `sleep` module
7 years ago
08f73b8420
Remove last processed index after attachment migration
7 years ago
696a144ab7
Add `settings.deleteItem`
7 years ago
a18e462817
Move migrations to `Signal.Migrations`
7 years ago
5910f84af4
Remove outdated documentation
7 years ago
efe3cd67fc
Allow attachment migration run on higher database version
7 years ago
921c3dba7c
Skip migrations that have already been applied
7 years ago
417511ffd2
Add `database.getVersion`
7 years ago
c5c94bc3ab
Extract `getMigrationVersions`
7 years ago
6aea36240d
Rename `closeDatabase` to `closeDatabaseConnection`
7 years ago
016432826b
Extract `database` and `settings` modules
7 years ago
5bea894abd
Close database connection via Backbone IDB adapter
7 years ago
f50e9ae364
Log closing connection of database
7 years ago
4ff8bc3357
Use `camelCase` for non-constructors
7 years ago
3720c3f3bb
Improve log message
7 years ago
ce5b450fdb
Log `targetSchemaVersion`
7 years ago
f7f24b5822
Log total number of processed messages
7 years ago
eca930770c
Remove hard-coded database connection settings
7 years ago
1df6dc8378
Abort processing if there are no more messages
7 years ago
85490fbc98
Disable JSHint for `background.js`
...
It doesn’t recognize `async` and I couldn’t figure out how to ignore a top-level
`async` without cascading errors.
7 years ago
d5d0eabdfd
Remove usage of `storage` module
7 years ago
8966e80284
Improve identifier names
7 years ago
3e2d575506
Document `MessageDataMigrator` module design
7 years ago
3c57dbfb56
Extract `NUM_MESSAGES_PER_BATCH`
7 years ago
85788d3c4a
Match `items` storage format to Backbone adapter
7 years ago
7de7fcf561
Avoid `no-param-reassign` violation
7 years ago
070235b59b
Implement `MessageDataMigrator.processAll`
...
Upgrades schema of all messags upon startup.
7 years ago
b8a0bc3423
Run attachment to disk migration on startup
7 years ago
178a3cc262
Reduce work for verifying transaction completion
7 years ago
b6e978f74c
Implement `MessagesDataMigrator.processAll`
7 years ago
457bf7ab9d
Add `createCollection` function
7 years ago
8ea257ad4d
Use double quotes for identifiers in error messages
7 years ago
172616ca4f
Add log message for dummy migration 18
7 years ago
579b01283e
Replace `wrapDeferred` with `deferredToPromise`
7 years ago
40c40c800a
Prefer `exports`
7 years ago
da144edc56
Manually close database connection after migration
7 years ago
106ce21c49
Remove redundant log message
7 years ago
fcd30cd919
Close database after migration
...
This is not 100% reliable as database connections are closed in a separate
thread according to the documentation:
- https://developer.mozilla.org/en-US/docs/Web/API/IDBDatabase/close
- https://stackoverflow.com/a/18639298
- 80c7a06d5c/backbone-indexeddb.js (L558-L565)
7 years ago
c765422fa1
Extract `deferredToPromise`
7 years ago
e2f1339ab9
Explicitly run post-attachment migrations
7 years ago
d7c8d33edb
Extract `runMigrations`
7 years ago
d16178638e
Split database migrations into pre- and post-attachment migration
...
- Run light-weight migrations before attachment migration.
- Run regular migrations after attachments have been moved to disk.
7 years ago
3841154295
Relax Node.js version requirements ( #2203 )
7 years ago
81ac6a9031
Don't lock the Node version so strictly
...
This is particularly problematic because Yarn apparently
errors (not warns) if the engine doesn't match.
7 years ago
f6d0c1f171
Fix contact overwrite in search view ( #2191 )
...
When typing in an existing phone number into the search, clicking on it even
though there exists an existing contact will reinitialize that contact’s
database entry. This reinitialization clears that contact’s conversation’s name,
unread count, etc.
This change ensures we always reuse existing conversations using
`ConversationController.getOrCreateAndWait` when starting new conversations in
the search view.
7 years ago
b24dad23ea
Fix search view conversation reset bug
...
When searching for an existing conversation using a phone number, it’s possible
to click on ‘Start conversation…’ and have that new dummy entry overwrite the
existing conversation.
This change ensures we are always showing a dummy conversation model that is not
part of the conversation collection. Adding it is always idempotent as it goes
through `getOrCreateAndWait`.
7 years ago
Daniel Gasienica
AJ Jordan