edfcore 0.4.331 → 0.4.333

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.331";
+export declare const VERSION = "0.4.333";
 //# 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.331';
+export const VERSION = '0.4.333';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.333
+
+- **Added** the rest of `migrating-to-0-3.md`: the difference the page calls structural. `sampleAt`
+  returns `undefined` for each of the three reasons the page gives — the instant falls in a gap,
+  before the recording, or after it — and returns a location either side of the hole, so that
+  `undefined` is a statement about the file rather than the function's usual answer.
+- The other half is that the grid form has no way to say it. Given only a signal and a record
+  duration it returns an index at every instant, including one past the end of the file, which is
+  checked against the record count. And both refuse a probed index on a file with gaps: the same
+  fixture throws before `buildRecordIndex` and answers after it, with `contiguityOf` reporting
+  `'unknown'` in between.
+
+## 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.331",
+  "version": "0.4.333",
   "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.331';
+export const VERSION = '0.4.333';