← Commit history

v0.16.56 (insiders): fix: the export's file-watch timestamp was used before it was declared, so every run died with 'Cannot access watchSince0 before initialization'

John Lauer ·2657e216de ·13d ago ·parent b00f36d
6 files changed +6−6
bin/nb-dashboard+1−1
@@ -20,7 +20,7 @@ const { execFile, spawn } = require('child_process'); const fs = require('fs'); const crypto = require('crypto'); -const VERSION = '0.16.55';           // keep in lockstep with package.json (pkg version)+const VERSION = '0.16.56';           // keep in lockstep with package.json (pkg version) // SEND TO AI IS UN-PARKED (John: "yeah, we are re-enabling the send to ai. it seems to be good now"). // The ah build thread certified the crash family dead on the gate-fixed build and the delivery leg is // proven end to end. The park const is DELETED rather than flipped, so no dead branch can resurrect it.
bridge/BRIDGE_VERSION+1−1
@@ -1 +1 @@-0.16.55\ No newline at end of file+0.16.56\ No newline at end of file
bridge/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "native-browser",   "displayName": "Adom Native Browser",-  "version": "0.16.55",+  "version": "0.16.56",   "expectedExtensionVersion": "0.2.22",   "description": "Drives the user's REAL signed-in Chrome/Edge, in two layers. Layer 1 (nb) needs NOTHING installed and works on any machine: nbrowser_open_os_window (open a URL in the user's real profile, background+flashing, the OAuth/consent path), nbrowser_os_windows, nbrowser_profiles, nbrowser_wake_profile, nbrowser_force_close. Layer 2 (nbe, the Adom Native Browser Extension) unlocks the rest: CDP driving (navigate/click/read/screenshot) inside their logged-in profile. The bridge binds an ephemeral loopback port and the native-messaging host pumps stdio <-> bridge.",   "homepage": "https://wiki.adom.inc/adom/nb-bridge",
bridge/package.json+1−1
@@ -1,6 +1,6 @@ {   "name": "adom-native-browser-bridge",-  "version": "0.16.55",+  "version": "0.16.56",   "private": true,   "description": "Native-browser bridge for Bridge (ab): layer 1 (nb) plus layer 2 via nbe, the Adom Native Browser Extension (Chrome + Edge).",   "main": "server.js",
bridge/server.js+1−1
@@ -3189,6 +3189,7 @@ async function exportSavedLogins(opts) {   const outDir = path.join(os.tmpdir(), 'adom-nb-export');   const csvPath = path.join(outDir, `logins-${Date.now()}.csv`);   try { fs.mkdirSync(outDir, { recursive: true }); } catch {}+  const watchSince0 = Date.now();   // everything that looks for the exported file measures from here   const step = (name, ok, detail) => ({ step: name, ok: !!ok, ...(detail ? { detail } : {}) });   const steps = [];   const cleanup = () => { try { fs.unlinkSync(csvPath); } catch {} };@@ -3305,7 +3306,6 @@ async function exportSavedLogins(opts) {   // should ever see here is the Hello prompt. So poll FAST and fill it the moment it exists, and keep   // waiting the whole budget - the dialog only appears AFTER they answer Hello, which can take a while.   await exportSay(`${brand} is asking you to confirm it is you (Windows Hello). Approve it and Adom finishes the rest - do not close anything.`);-  const watchSince0 = Date.now();   const watchSince = watchSince0;   const deadline = Date.now() + timeoutSec * 1000;   let saved = false, foundFile = null, toldToSave = false;
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "nb-bridge",-  "version": "0.16.55",+  "version": "0.16.56",   "type": "app",   "title": "NB - Native Browser Bridge",   "description": "This package installs the SKILLS into your container so your AI knows how to drive your real signed-in Chrome and Edge; Bridge loads the bridge runtime itself from the release zip.",