[P2] macOS compiled SharpPaint initial Gaussian preview can remain in settings until timeout

Open
  • Is something wrong?
#3,492 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
testing-qa

Research direction

Read SharpPaintHeadlessTests.WorkflowsPass and the retained log at artifacts/p3-compiler/fresh-b37-ci/gui-macos-arm64-complete.log (lines 249–287), then inspect the preview setup, debounce, and queued raster/decode/filter work. On a recurrence, capture the scheduling, job, and render trace to identify the cause. Done means a causal fix is demonstrated while retaining the 180 ms debounce, 15-second readiness guard, workflow assertions, and process cleanup budget.

Written by the indexing model from the issue text.

Description

A macOS ARM64 GUI-conformance run observed the compiled SharpPaint editing workflow fail at its first Gaussian-blur preview. The visible status remained Gaussian blur settings until the existing 15-second wait for Effect preview ready expired. This blocks the preview feature in the observed run; the cause and a reliable reproducer remain unknown.

Observed source: b37b66863efe3cc86326ef475cfc73a9b487dec0. That commit changes only standalone CI capacity; the preceding b638983ca source has identical production behavior and its macOS GUI run passed. Neither commit is established as the introduction of this failure.

Retained complete log: artifacts/p3-compiler/fresh-b37-ci/gui-macos-arm64-complete.log, lines 249–287. The run reports 133 passes and one failure in SharpPaintHeadlessTests.WorkflowsPass(mode: "compiled", scenario: "editing", expectedWindows: 2):

  • Text passed at 9.224 seconds.
  • Gaussian blur settings at 24.698 seconds.
  • Error: Timed out: Effect preview ready at 24.701 seconds.

The reported raw trace was /var/folders/y3/p6x0rn5562l5qyxy7x6jqrsc0000gn/T/sharpts-sharpaint-compiled-eb97d5e5d0784add871ef254e360f539/compiled.json. It was not uploaded: the test deleted its temporary stage during cleanup, and the workflow artifact list did not include that location. #3490 addresses trace retention for subsequent failures.

Investigation found that preview setup synchronously serializes the document and adapts the returned task, while raster/decode/filter work is queued using Task.Run. Absence of the later busy label alone does not prove whether the debounce callback ran. An artifact-only instrumented Windows run observed initial debounce fire after 181 ms, synchronous setup below 1 ms, and preview completion after 51 ms; it does not explain or fix the macOS failure.

#3491 addresses a separate, demonstrated stale-ready/old-result problem after changing parameters. This failure occurred before the initial preview was ready and must not be attributed to that fix without new evidence.

Retain the existing 180 ms debounce, 15-second readiness guard, full workflow assertions, and process cleanup budget. Capture the scheduling/job/render trace on recurrence and identify a causal fix. A later passing run is evidence of that run only, not proof that this failure is fixed.

Dominant language
C#
Stars
156
Forks
4
Avg merge
15h 1m
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nickna/SharpTS

All issues in nickna/SharpTS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.