edfcore 0.4.385 → 0.4.387

package/README.md

@@ -78,7 +78,7 @@ for (const event of annotations) {
 }
 ```
 
-> **Status: 0.4.x, early.** edfcore runs 1,900+ tests on generated fixtures, and it's checked
+> **Status: 0.4.x, early.** edfcore runs 2,000+ tests on generated fixtures, and it's checked
 > against public corpora it didn't author: the EDF, EDF+ and 24-bit BDF+ test files from
 > teuniz.net, and PhysioNet's sleep-edfx (a real 22-hour polysomnography recording and its
 > sleep-staging file). Those checks are numeric. Channels labelled `sine 8.5 Hz` decode to

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

package/docs/CHANGELOG.md

@@ -6,6 +6,43 @@ 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.387
+
+- **Added** a check that the published `bin` runs as a program. `cli.test.ts` and the rest drive
+  `runCli` through an injected `CliIo`, deliberately, so they need no build; `cli-pipe.test.ts`
+  spawns the built file but always as `node dist/cli.js`, naming the interpreter itself. Between
+  them they covered every line of the program and none of the mechanism that starts it.
+- Delete the `#!/usr/bin/env node` from `src/cli.ts` and every test here still passes: the build
+  succeeds, `verify:tarball` finds the bin target in the tarball, and `node dist/cli.js header
+  f.edf` works exactly as before. `npx edfcore header f.edf` — the first command the README prints
+  — fails on the first line of JavaScript, because the shell it was handed to is not a JavaScript
+  engine.
+- So the built file is given the executable bit npm's tarball carries for a bin and run with no
+  interpreter named, which is the only way to check the shebang rather than the file's first line:
+  a CRLF ending, a leading blank line or a BOM each leave the text intact and the program
+  unloadable.
+- Both spawns close stdin and carry a timeout, because that failure does not look like an error. A
+  file with no shebang is handed to `/bin/sh`, which reads JavaScript as shell and sits waiting for
+  input — without the timeout a deleted shebang hangs the suite instead of failing it.
+
+## 0.4.386
+
+- **Added** a property test for the window rule annotations are filtered by: overlap rather than
+  containment for an event with a duration, and half-open containment of the onset for an instant,
+  so adjacent windows partition a recording without double-counting the boundary.
+- `tests/unit/annotations-query.test.ts` checks that with hand-placed events at hand-picked
+  boundaries and is thorough about the cases someone thought of — the instant at t = 0, the epoch
+  ending exactly where the window starts, the duration a writer spelled `0` rather than omitting.
+  What no example can say is that the rule holds for a partition it was not written against.
+- So the events are generated, written into a real EDF+ file and read back through the parser
+  before anything is filtered. The comparison is on `onsetTicksFromFirstRecord`, and those ticks
+  are parsed digit by digit out of the TAL: an oracle fed hand-built objects would agree with the
+  filter about numbers no file ever produced.
+- Three properties over that: every instantaneous event gets exactly one window of a partition,
+  an event with a duration gets every window it overlaps and no other, and the result matches an
+  independent case analysis in ticks. Changing `onset >= from` to `onset > from` in the filter —
+  one character — fails the first two with a shrunk counterexample.
+
 ## 0.4.385
 
 - **Added** a check that the file the inspector hands a first-time visitor is one edfcore accepts.

package/package.json

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