Skip to content

fix(blender): OpenCode for Blender 0.4.8, say what became of a Blender that stops answering - #30

Merged
pascalandr merged 1 commit into
mainfrom
feat/blender-0.4.8
Nov 15, 2026
Merged

pascalandr merged 1 commit into
mainfrom
feat/blender-0.4.8

Conversation

@pascalandr

Copy link
Copy Markdown
Collaborator

OpenCode for Blender 0.4.8, from the Sol trial where two Blenders seemed to vanish.

Causes. ex06: the agent's script set use_disk_cache on the rigid body world's point cache of a saved file; Blender 5.3 crashes there (ptcache_filepath, a Blender defect). On Windows the crashed Blender stays open behind its crash window: the call waited its whole timeout, then the offer vanished (No Blender is offered), while the crash report was written in the first second. ex02: the QA's clean-up stopped the Blenders naming ex02 (17:32:27) during a verify with saved; the plugin's process has ended, with no crash report was right. Two conversations had attached that Blender (allowed, documented). A busy Blender keeps its offer: its other Python threads run during a bake.

What a call says now. Crashed (the running call watches its Blender's crash report and stops within 2 s; process still open behind the crash window); closed without a report; still running a call that outlasted its wait or refused as busy (new add-on status method, answered off Blender's main thread); not answering; offer no longer renewed. After a crash or close, no other Blender attaches itself in its place. Only the report named after the Blender's document counts. An explicit attach to a Blender another conversation uses says so (shared).

Validation. A background Blender test and a plugin test fail on 0.4.7 (5c0b1de) and pass; in an interface Blender on a hidden desktop the trial's ex06 script answers Blender crashed after 2.1 s instead of the call's whole wait. lint, typecheck, npm test, build, check:markers, trace scan, Blender suites (26/26, extension 1/1), native sessions with OpenCode 2.2.5.

…r that stops answering

In the Sol trial two Blenders seemed to vanish. Their causes, established
from the transcripts and replayed:

- ex06: the agent's script set use_disk_cache on the rigid body world's
  point cache of a saved file. Blender 5.3 crashes there (ptcache_filepath,
  a Blender defect, reproduced in background and in an interface Blender on a
  hidden desktop). On Windows the crashed Blender stays open behind its crash
  window, so the call waited its whole timeout ("did not answer in time"),
  then the offer, no longer renewed, vanished: "No Blender is offered", while
  Blender's crash report had been written in the first second.
- ex02: the QA's own clean-up stopped every Blender whose command line named
  ex02 (17:32:27), the open one and the background Blender of a verify with
  saved, during that verify. The plugin's "process has ended, with no crash
  report" was right. Two conversations had also attached that Blender: the
  plugin allows it, as documented.

A busy Blender is not the cause: during a bake run by an operator, as during
a long Python loop, its other Python threads keep running (largest gap 0.5 s),
so its advertiser keeps its offer.

What a call says now:
- crashed: a running call watches its Blender's crash report and stops
  waiting within two seconds: "Blender crashed: crash report <path>. Its
  process is still open (Blender's crash window)"; later calls say the same;
- closed without a report: "closed, or ended by another program";
- still running a call that outlasted its wait, or refused as busy: the
  add-on's new status method, answered off Blender's main thread, names the
  request its main thread runs and for how long;
- not answering: the process runs but OpenCode Link answers nothing in 3 s;
- offer gone while the process runs, without a report: it stopped renewing.
After its Blender crashed or closed, a conversation never attaches another
Blender by itself; a detach forgets it. Only the report named after the
Blender's own document counts: every Blender of a user writes in one folder.
An explicit attach to a Blender another conversation uses says they share
one document (shared).

Validation: a background Blender test (a call outlasting its wait, a crash
report appearing during a call with the process open, an offer no longer
renewed) and a plugin test (shared attach) fail on 0.4.7 (5c0b1de) and pass;
unit tests for the reports. In an interface Blender on a hidden desktop, the
trial's ex06 script now answers "Blender crashed" after 2.1 s instead of the
call's whole wait. lint, typecheck, npm test, build, check:markers, trace
scan, the Blender suites (26/26, extension 1/1) and native sessions with
OpenCode 2.2.5 pass.
@pascalandr
pascalandr merged commit 903fa2d into main Nov 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant