edfcore 0.4.276 → 0.4.277

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.276";
112
+ export declare const VERSION = "0.4.277";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.276';
82
+ export const VERSION = '0.4.277';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.277
10
+
11
+ - **Fixed** a test budget that has now been wrong twice, by making it a different kind of number.
12
+ `extreme-geometry.test.ts` asserts that a diagnostic per record does not blow the call stack —
13
+ `TIMEKEEPING_TAL_MISSING` is per record, and `push(...array)` gives up around 125,000 arguments
14
+ — and it carried a 30 second timeout. How long the sweep takes is not the property. A timeout
15
+ set just above the observed duration measures the machine instead of the code, and reports a red
16
+ build in something the test does not touch.
17
+ - It started at vitest's 5 second default, which the 200,000-record sweep landed a few hundred
18
+ milliseconds under on its own, so it tipped over whenever the rest of the suite ran beside it.
19
+ Thirty seconds fixed that and repeated the mistake one size up: the suite kept growing — 2,074
20
+ tests now, one of which spawns a TypeScript compiler over 102 files — and on a machine already
21
+ busy with unrelated work the sweep took 72 seconds and failed again. It is five minutes now, and
22
+ named for what it is: an infinite loop still fails, a loaded laptop does not.
23
+
9
24
  ## 0.4.276
10
25
 
11
26
  - **Added** the check for the other ban `AGENTS.md` lists: "No `Date` anywhere. EDF stores local
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.276",
3
+ "version": "0.4.277",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.276';
96
+ export const VERSION = '0.4.277';