recovery-probe 0.4.0-preview.4 → 0.4.0-preview.5
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/CHANGELOG.md +6 -0
- package/README.md +1 -1
- package/docs/observe.md +1 -1
- package/docs/repair.md +1 -1
- package/package.json +1 -1
- package/src/repair.mjs +19 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,12 @@ All notable changes to Recovery Probe are documented here. The project follows [
|
|
|
4
4
|
|
|
5
5
|
Version 0.2.0 is the first npm release. Earlier 0.1.x revisions were repository-only prototypes.
|
|
6
6
|
|
|
7
|
+
## 0.4.0-preview.5 (2026-10-16)
|
|
8
|
+
|
|
9
|
+
- Repair on Windows: the isolated checkout now holds the committed bytes instead of the CRLF line endings Git for Windows writes by default. A multi-line proposal with LF line breaks previously failed with "find text must match exactly once". `eol` rules in `.gitattributes` still apply.
|
|
10
|
+
- Repair on Windows: a committed symlink selected as a source is rejected again. Without symlink rights, Git for Windows checks it out as a plain file, which passed the old check; sources are now checked against the index.
|
|
11
|
+
- CI runs the repair pipeline on Windows.
|
|
12
|
+
|
|
7
13
|
## 0.4.0-preview.4 (2026-10-15)
|
|
8
14
|
|
|
9
15
|
- `createFaultFetch` passes relative URLs, such as `fetch('/api/x')`, to the supplied fetch untouched. Previously they threw `Invalid URL`.
|
package/README.md
CHANGED
|
@@ -77,7 +77,7 @@ If no request matches, `withFault` throws `FAULT_NOT_TRIGGERED` instead of letti
|
|
|
77
77
|
|
|
78
78
|
## Install
|
|
79
79
|
|
|
80
|
-
**0.3.0** is the stable release on npm's `latest` channel, and the commands above pin it for reproducible reports. The 0.4 observation preview is `recovery-probe@0.4.0-preview.
|
|
80
|
+
**0.3.0** is the stable release on npm's `latest` channel, and the commands above pin it for reproducible reports. The 0.4 observation preview is `recovery-probe@0.4.0-preview.5` on the `next` channel; install it with the same Playwright version.
|
|
81
81
|
|
|
82
82
|
Use Node.js 22 or newer. A separate tools folder keeps the tester out of your application's production dependencies. Browser and desktop commands need Playwright; attached targets use their existing browser runtime. If a version is not on npm yet, use the [source installation](CONTRIBUTING.md#install-an-unpublished-source-preview): a GitHub merge alone does not publish the package. See [CHANGELOG.md](CHANGELOG.md) for version history.
|
|
83
83
|
|
package/docs/observe.md
CHANGED
|
@@ -108,7 +108,7 @@ Tracking ends at the next operator interval or capture termination, including in
|
|
|
108
108
|
|
|
109
109
|
## Actions, tracked rows and delayed UI updates
|
|
110
110
|
|
|
111
|
-
Available from **0.4.0-preview.1**. The current preview target is **0.4.0-preview.
|
|
111
|
+
Available from **0.4.0-preview.1**. The current preview target is **0.4.0-preview.5** on npm `next`; install it explicitly with `npm install --save-dev --save-exact recovery-probe@0.4.0-preview.5 playwright@1.62.1`. The development IPC hook must come from the same version.
|
|
112
112
|
|
|
113
113
|
These options are opt-in and extend the same fault-free capture. They answer "how long after the user's action did the screen show the right state, and did data arrive before it?"
|
|
114
114
|
|
package/docs/repair.md
CHANGED
|
@@ -75,7 +75,7 @@ These `web`/`desktop` checks never call an AI provider. Read their local reports
|
|
|
75
75
|
|
|
76
76
|
## Configure a repair run
|
|
77
77
|
|
|
78
|
-
The repair runner must launch a **separate build from its own checkout**, not attach to the existing app. Stop whatever is using the configured test port. Commit or stash all changes, including untracked files, in the source repository first. Ignored `.env` files, dependencies and local credentials are not copied into the checkout. Use a disposable dev environment with nonproduction settings. Your configured setup commands must prepare whatever that build needs; secret environment variables are not inherited automatically.
|
|
78
|
+
The repair runner must launch a **separate build from its own checkout**, not attach to the existing app. Stop whatever is using the configured test port. Commit or stash all changes, including untracked files, in the source repository first. Ignored `.env` files, dependencies and local credentials are not copied into the checkout. The checkout holds the committed bytes: Git line-ending conversion is off there, so on Windows its files keep LF line endings where your working tree has CRLF. `eol` rules in `.gitattributes` still apply. Use a disposable dev environment with nonproduction settings. Your configured setup commands must prepare whatever that build needs; secret environment variables are not inherited automatically.
|
|
79
79
|
|
|
80
80
|
Create `portal-repair.json` in the tools folder, outside the app repository:
|
|
81
81
|
|
package/package.json
CHANGED
package/src/repair.mjs
CHANGED
|
@@ -336,11 +336,18 @@ export async function prepareRepair(
|
|
|
336
336
|
await mkdir(dir, { mode: 0o700 }) // Never overwrite or reuse a run.
|
|
337
337
|
const baseCommit = (await git(repo, ['rev-parse', 'HEAD'])).trim()
|
|
338
338
|
const workspace = join(dir, 'checkout')
|
|
339
|
+
// Check out the committed bytes, whatever this machine's Git converts. Git for Windows
|
|
340
|
+
// writes CRLF by default, and a model's multi-line edit with LF breaks would not match.
|
|
341
|
+
// Explicit eol attributes in .gitattributes still apply.
|
|
339
342
|
await git(dir, [
|
|
340
343
|
'clone',
|
|
341
344
|
'--local',
|
|
342
345
|
'--no-hardlinks',
|
|
343
346
|
'--no-checkout',
|
|
347
|
+
'--config',
|
|
348
|
+
'core.autocrlf=false',
|
|
349
|
+
'--config',
|
|
350
|
+
'core.eol=lf',
|
|
344
351
|
'--',
|
|
345
352
|
repo,
|
|
346
353
|
workspace,
|
|
@@ -349,7 +356,18 @@ export async function prepareRepair(
|
|
|
349
356
|
await git(workspace, ['remote', 'remove', 'origin']) // No accidental push target.
|
|
350
357
|
const sources = []
|
|
351
358
|
for (const path of config.sourceFiles) {
|
|
352
|
-
|
|
359
|
+
// The index says what a path is. Without symlink rights, Git for Windows checks out
|
|
360
|
+
// a committed symlink as a plain file holding the link text.
|
|
361
|
+
const [mode] = (
|
|
362
|
+
await git(workspace, [
|
|
363
|
+
'ls-files',
|
|
364
|
+
'--stage',
|
|
365
|
+
'--error-unmatch',
|
|
366
|
+
'--',
|
|
367
|
+
path,
|
|
368
|
+
])
|
|
369
|
+
).split(' ')
|
|
370
|
+
if (mode === '120000') throw new Error('Source symlinks are not allowed')
|
|
353
371
|
const content = await sourceFile(workspace, path)
|
|
354
372
|
sources.push({ path, content, sha256: sha(content) })
|
|
355
373
|
}
|