You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3fd4cdd
Browse filesBrowse the repository at this point in the historyBrowse files
[agent] 2026-10-01: Deno bug-hunt run (addendum to 20261001T021734Z; same main `2463257`)
2
+
3
+
Same session, extended. No new issues were filed; all new findings went onto existing issues.
4
+
5
+
### Cells
6
+
-**fail #406 (vendored, new information):** in the mixed project (package.json + package-lock.json + deno.lock), `scan --mode vendored` rewires package-lock.json to `file:.socket/vendor/...`, reports `applied` / success, and leaves deno.lock untouched. `deno install --frozen` loads the unpatched copy. `vex` keeps attesting `not_affected`*after* the Deno install, warning only `vendored_tree_out_of_sync` with a "re-run your package manager's install" remedy that can't work under Deno. Deno 2.2.15 and 2.9.6. This also contradicts the ecosystems.md Deno row ("vendored ❌ refused"). Comment: https://github.com/SocketDev/socket-patch/issues/406#issuecomment-5923419446
7
+
-**fail #406 (Deno 1.46.3, deno.lock v3):** hosted is the same. Comment: https://github.com/SocketDev/socket-patch/issues/406#issuecomment-5923422888
8
+
- pass: `scan --mode agent --global-prefix vendor/jsr.io` discovers, downloads and applies a JSR patch, and the patched code runs.
9
+
- caveat (#374): `--global-prefix` re-roots every crawler, so in a mixed JSR + npm project the npm deps vanish. `apply` gives success with `package_not_installed`, and `--prune` would delete npm records. Documented semantics, so not a separate bug. Comment: https://github.com/SocketDev/socket-patch/issues/374#issuecomment-5923430317
10
+
11
+
### Harness note
12
+
The stub's vendored path needs the served tarball to carry the same after-bytes as the patch view. A mismatch gives `apply_failed` ("prebuilt tarball … does not carry the patched files"), which is a harness artifact, not a bug.
13
+
14
+
### Next
15
+
1. pnpm-lock.yaml / yarn.lock / bun.lock beside deno.lock (expected to be the same #406 class; confirm before commenting).
16
+
2.`.deno` peer-variant and scoped transitive entries, once #373 is fixed.
@@ -20,7 +20,7 @@ Other passes (Linux): re-apply idempotency, rollback, `remove`, breaking cache h
20
20
## Backlog
21
21
22
22
0. A maintainer needs to delete the stale probe branches `bughunt/deno/20260930-deno-store` and `bughunt/deno/20261001-scoped-jsr`. The git proxy refuses `push --delete`.
23
-
1.#406 follow-ups: Deno 1.46.3 with package.json; pnpm-lock / yarn.lock / bun.lock beside deno.lock; vendored takeover in a mixed project.
23
+
1.#406 follow-ups: pnpm-lock / yarn.lock / bun.lock beside deno.lock. Done: Deno 1.46.3 (affected) and vendored (affected, and VEX survives the install).
24
24
2.`.deno` peer-variant and scoped transitive entries, once #373 is fixed.
25
25
3. Hosted `get` / `scan` for `pkg:jsr` against the real proxy (the stub can't decide the real grant status).
26
26
4.`nodeModulesDir: none`: deno.lock as a lockfile supplement (enhancement).
0 commit comments