machinaos 0.0.82 → 0.0.83

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "react-flow-client",
3
3
  "private": true,
4
- "version": "0.0.82",
4
+ "version": "0.0.83",
5
5
  "type": "module",
6
6
  "scripts": {
7
7
  "start": "vite --host 0.0.0.0",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "machinaos",
3
- "version": "0.0.82",
3
+ "version": "0.0.83",
4
4
  "description": "Open source workflow automation platform with AI agents, React Flow, and n8n-inspired architecture",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -126,16 +126,20 @@ if (uvVersion) {
126
126
  }
127
127
  }
128
128
 
129
- // Temporal binary: downloaded on first backend boot by
130
- // server/services/temporal/_install.py via pooch (~90 MB tarball
131
- // cached under platformdirs.user_cache). No global npm install.
132
- // User-installed `temporal` on PATH (brew / scoop / cargo) is still
133
- // honoured by the Python supervisor's shutil.which fallback.
129
+ // Temporal binary: downloaded eagerly during install (step [6/6])
130
+ // by ``python -m services.temporal._install``, same call ``machina
131
+ // build`` already makes. The pooch cache (~/.cache/MachinaOs/...)
132
+ // makes re-runs sub-second. Done eagerly because
133
+ // ``TemporalServerRuntime._pre_spawn`` unconditionally calls
134
+ // ``ensure_temporal_binaries`` -- the runtime always uses the
135
+ // pooch-downloaded binary regardless of any system ``temporal`` on
136
+ // PATH -- so pre-fetching here eliminates a 30-90 s stall on the
137
+ // user's first ``machina start``.
134
138
  let temporalVersion = getVersion('temporal --version');
135
139
  console.log(
136
140
  temporalVersion
137
- ? ` temporal: ${temporalVersion} (system install, will be reused)`
138
- : ' temporal: managed by Python backend (pooch download on first boot)',
141
+ ? ` temporal: ${temporalVersion} (system install, pooch copy installed below)`
142
+ : ' temporal: not on PATH, pooch copy installed below',
139
143
  );
140
144
 
141
145
  // agent-browser is managed by the Python backend
@@ -156,7 +160,7 @@ try {
156
160
  // Calculate total steps
157
161
  let totalSteps = 1; // .env always
158
162
  if (!clientDistExists) totalSteps += 2; // client deps + build
159
- totalSteps += 3; // Python deps + bytecode compile + CLI venv
163
+ totalSteps += 4; // Python deps + bytecode compile + CLI venv + Temporal binary
160
164
  let step = 0;
161
165
 
162
166
  // Create .env if needed
@@ -228,6 +232,18 @@ try {
228
232
  }
229
233
  run(`uv pip install --python "${cliVenvPython}" --quiet -e .`, ROOT);
230
234
 
235
+ // Eagerly fetch the official Temporal CLI binary (~90 MB tarball
236
+ // from temporal.download/cli/archive/latest). Same call ``machina
237
+ // build`` step [6/6] makes. The runtime supervisor unconditionally
238
+ // uses this pooch-cached copy via
239
+ // ``TemporalServerRuntime._pre_spawn`` -- it ignores any system
240
+ // ``temporal`` on PATH -- so pre-fetching at install time turns a
241
+ // 30-90 s stall on first ``machina start`` into a sub-second
242
+ // cache hit. Idempotent on re-install (pooch cache).
243
+ step++;
244
+ console.log(`[${step}/${totalSteps}] Installing Temporal binaries...`);
245
+ run('uv run python -m services.temporal._install', serverDir, 600000);
246
+
231
247
  // WhatsApp RPC is now an npm dependency - binary downloaded via postinstall
232
248
  console.log('');
233
249
  console.log('Done!');