Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
9 check-ins related to "sahpool-digest"
|
2025-03-16
| ||
| 14:05 | Fix a long-standing filename digest computation bug in the OPFS SAHPool VFS which caused all VFS-stored filenames to have a digest value of 0. See /forumpost/042d53c928382021 for full details. (check-in: 493cbe7450 user: stephan tags: trunk) | |
|
2025-03-14
| ||
| 11:14 | Minor doc corrections for the sahpool-digest fix and merge in current trunk. (Closed-Leaf check-in: 500f2e6ec7 user: stephan tags: sahpool-digest) | |
| 09:34 | Cherrypick the [2b582c0097e33] doc addition, which was initially committed to the wrong branch. (check-in: f786de8d18 user: stephan tags: trunk) | |
|
2025-02-26
| ||
| 03:32 | Merge trunk into the sahpool-digest branch. (check-in: fc1eeb7d1f user: stephan tags: sahpool-digest) | |
| 03:20 | Fix a bug in mkwasmbuilds.c, introduced in [e4539ebebd89], which caused sqlite3.wasm to get deleted directly after it was built. (check-in: 1a72d1d13e user: stephan tags: trunk) | |
| 03:03 | More work on the sahpool digest fix. New/fixed versions can read legacy (no digest) files but the reverse is only possible in limited circumstances (when files originated from a legacy version). The burning question is whether the real fix would be to remove this digest check altogether, as it only applies in a very limited context, and the fact that it was broken for some 18 months unnoticed suggests that its value might not be worth the CPU cycles. (check-in: 0df62b776c user: stephan tags: sahpool-digest) | |
|
2025-02-03
| ||
| 17:21 | Add a test app to assist in validating the SAHPool digest calculation fix. (check-in: a1e304b802 user: stephan tags: sahpool-digest) | |
| 16:26 | Initial work on a fix for the SAHPool VFS's effectively-no-op digest calculation, as reported in ticket #97 of the downstream npm subproject. This requires more testing alongside databases created before this version to ensure that it's backwards-compatible. (check-in: 9234c33f92 user: stephan tags: sahpool-digest) | |
| 14:55 | Add a more complete test for [76c8435a] and add some commentary about (A) the inability to automatically clean up automatically-generated WASM proxy functions for sqlite3_set_auxdata() destructors and (B) how to deal with (A) to avoid leaking WASM proxy functions. (check-in: d693c2dddb user: stephan tags: trunk) | |