Repository navigation
Conversation
…at it failed to reach A container's http_proxy swallowed the health check of a 127.0.0.1 editor url and the miss was read as "no editor is running" — both the record's url (now always the loopback) and the check (now a proxy-bypassing opener) are fixed, and a record whose server does not answer is an error naming the record and url, not a silent fallthrough. Reading the file as a fallback says so on stderr. Cell feedback: put/insert/run carry console and the not-healthy dependents, the swept dependents run, and a failing cell names its upstream (the failing ancestors first) with marimo's own dependency semantics. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…eter logs sca run --through N runs the first N cells the way the editor numbers them (the setup cell takes no number), --no-product runs a work-in-progress notebook that has no product yet, and --timeout (default 120s) fails a run that takes longer instead of hanging the agent. The cache loaders' degraded- state warnings (unsigned entries, stub restores) no longer print at WARNING, and VTK's own chatter (a missing X server) is off; a real failure is still raised and named. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… wording; git discipline Printing an inspection now shows a one-line digest (the per-face records are to_dict()/.faces). The skill says what an agent in a shared editor needed told: while an editor runs, sca cell is the only way to change a regular cell — the file only when no editor runs or for the cells sca cell refuses. dof=0 says the constraint system closed, not that the shape is right (mirror solutions); verify by measurement. And a modeling project is managed like software: git from the first file, commits at verified milestones, generated state ignored. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…write that outlives its call says the edit landed sca run --timeout now defaults to no limit (the runner's own default): a command that never timed out does not grow a hard failure; --timeout 240 was verified against a real fillet notebook through the worker thread. sca cell write calls time out with "the edit was applied and the rerun is still going; check sca cell ls" instead of a raw socket error, and the wait is SCA_EDITOR_CALL_TIMEOUT (default 300s). A server.json whose pid is gone reports the stale record and the remedy, not an unreachable url. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
From a FormerOS container agent's field report (via sca-promo):
sca run --through N / --no-product / --timeout(default 120s).Test plan