edfcore 0.4.330 → 0.4.332

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.330";
+export declare const VERSION = "0.4.332";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.330';
+export const VERSION = '0.4.332';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,29 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.332
+
+- **Fixed** a test of mine that could time out. The UTF-8 sweep added in 0.4.324 encoded each of
+  the 1.1 million code points above U+007F on its own and walked the result with an iterator, which
+  took about 2.6 seconds alone and over five under a loaded suite — past the default timeout. It
+  had passed every run until the suite grew enough to starve it.
+- Now encoded in blocks and scanned by index. UTF-8 is context-free, so the bytes of a run of code
+  points are the concatenation of each one's, and the check covers the same 4,382,464 bytes in
+  about a tenth of the time. Raising the timeout was the other option and the wrong one: it would
+  have left a five-second check running on every commit to prove something that takes a third of a
+  second to prove.
+
+## 0.4.331
+
+- **Added** an execution of the example `migrating-to-0-3.md` builds its whole argument on: on a
+  file with a seven-second hole after record 2, the grid form puts sample 12 at 3 seconds and the
+  recording-aware form puts it at 10. Both numbers, the size of the hole and the record it follows
+  are read out of the page, and the fixture is built from them.
+- The sentence the rename exists for is checked too, from the other side: before the hole the two
+  forms return the same number for every sample, which is exactly why the difference was easy to
+  miss. And the gap accounts for the whole of the difference after it — the page says both numbers
+  are correct about different things, and this is the arithmetic that makes that true.
+
 ## 0.4.330
 
 - **Added** a check over `migrating-to-0-3.md`, which was one of four documentation pages no test

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.330",
+  "version": "0.4.332",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.330';
+export const VERSION = '0.4.332';