edfcore 0.4.416 → 0.4.418
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +29 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.4.418";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,35 @@ 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.418
|
|
10
|
+
|
|
11
|
+
- **Fixed** the rest of what 0.4.417 was about. Memoising the diagnostic sweep cut
|
|
12
|
+
`spec-references.test.ts` from 13.0 s to 4.4 s and did not settle the timeouts: whichever check
|
|
13
|
+
ran first still did the whole sweep inside its own five-second budget, and on a machine running a
|
|
14
|
+
video call and an emulator that alone took 6.5 s. Three release runs failed on it after the
|
|
15
|
+
memo landed.
|
|
16
|
+
- The sweep is now paid for in a `beforeAll` with a timeout of its own. The work is real rather
|
|
17
|
+
than a hang, so the honest answer is to say how long it may take — once, in one place, rather
|
|
18
|
+
than as a number repeated on seven checks. Every check then finds the memo warm and runs at the
|
|
19
|
+
default timeout, which is the budget that should govern a check.
|
|
20
|
+
- Worth stating plainly: the previous entry claimed more than it delivered. It reduced the risk by
|
|
21
|
+
more than a factor of five and left the first caller carrying the whole cost.
|
|
22
|
+
|
|
23
|
+
## 0.4.417
|
|
24
|
+
|
|
25
|
+
- **Fixed** the cost of `spec-references.test.ts`, which was the most expensive file in the suite by
|
|
26
|
+
a wide margin. Seven checks in it ask questions of the same set of diagnostics, and each rebuilt
|
|
27
|
+
it from scratch: nine targeted parses plus 2,700 bit-flipped ones, seven times over. The sweep is
|
|
28
|
+
now run once for the file. It drops from 13.0 s to 4.4 s, and the work inside the tests from
|
|
29
|
+
10.3 s to 1.9 s.
|
|
30
|
+
- The reason to care is not the seconds. Every one of those seven checks sat within reach of
|
|
31
|
+
vitest's default 5 s timeout, which makes a test that passes or fails on how busy the machine is —
|
|
32
|
+
and two of them did fail, on a laptop running a video call and an emulator, for reasons that have
|
|
33
|
+
nothing to do with the code. A shared CI runner is the same machine on a bad day, and
|
|
34
|
+
`scripts/release.mjs` gates the tag on CI going green.
|
|
35
|
+
- Memoised rather than hoisted to a module-level `await`, so the sweep starts when the first check
|
|
36
|
+
asks for it and a rejection surfaces inside a test rather than as an unhandled one.
|
|
37
|
+
|
|
9
38
|
## 0.4.416
|
|
10
39
|
|
|
11
40
|
- **Added** tests for a file with no annotations signal, whose record onsets are arithmetic. Plain
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED