Diagnose stalled native execution before saved/reopen checkpoint
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
The first real existing-design checkpoint produced schema-valid output but hit the 180-second phase deadline before reporting execution success or saving a design. Reopening and phase two did not run. Originals and owned-process cleanup are retained; the cause remains unknown.
Scope: diagnose the exact blocked automation call and any dialog on the alternate display, then qualify the smallest correction to this existing-design workflow. Preserve the frozen source, input, XML expectations, original timeout, and process-ownership evidence. Keep production APIs, generated backends, new mapping representations, and timeout expansion outside this issue.
Depends on #281 and #283; blocks the real saved/reopen acceptance in #263. The output file alone does not establish successful execution or parity.
Acceptance:
- Independently review the original timeout, complete output, source custody, and final owned-process closure.
- Capture the exact stalled call and relevant alternate-display state without modifying the original run.
- Review and qualify a narrowly scoped correction with unchanged independent expectations.
- Complete a fresh saved/reopen cycle and full saved-structure/output review, or record a precisely evidenced remaining limitation.
Current result: independent review confirms that the complete partial output matches the frozen XML profile, source custody is unchanged and all owned processes are closed—not that execution or saving succeeded. The bounded diagnostic source is independently accepted; actual-result review, separate diagnostic controls and a fresh native run remain pending.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 571
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DeandreT/ferrule
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
test(mfd): synthetic whole-design MFD corpus with a stage-outcome ledgerPossibly taken @DeandreT claimed this today. Open
DeandreT/ferrule#1396 · 1 assignee ·
Maintainers usually reply within 1 day
-
arch: one built-in function catalog and shared limit definitionsPossibly taken @DeandreT claimed this 1 day ago. Open
DeandreT/ferrule#1390 · 1 assignee ·
Maintainers usually reply within 1 day
-
arch: type schema roles and format optionsPossibly taken @DeandreT claimed this 1 day ago. Open
DeandreT/ferrule#1389 · 1 assignee ·
Maintainers usually reply within 1 day
-
arch: remove downward dependencies on format adaptersPossibly taken @DeandreT claimed this 1 day ago. Open
DeandreT/ferrule#1388 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in DeandreT/ferrule
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
madesroches/fontaine#513 ·
Maintainers usually reply within 1 day
-
area:ui needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bherbruck/solvecraft#13497 ·
-
needs-triage tooling
Difficulty 1/5 Under an hour Newbie friendliness 90/100
neilsh/stunt-reel#317 ·
Maintainers usually reply within 1 day
-
Add Noto Sans Thaana (Dhivehi) - missing face blocking Thaana support in PdfCraftPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
storytold/craft-fonts#65 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
storytold/craft-libs#723 ·
Maintainers usually reply within 1 day