maniator / maniator/verticopolis
[Feature]: [P3] Wine harness headless loader flakiness (watch-only)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Imported from the engineering backlog (
_bmad-output/implementation-artifacts/backlog.md, storysimtower-wine-harness).
Priority P3 (do-first order) | Severity: low | Status: open | Epic: tooling | Type: review-deferral | Recorded: 2026-07-13
Problem / motivation
Gated (Wine-internal, watch-only). The tools/simtower headless load intermittently pops a winevdm.exe "serious problem" crash dialog that parks over the tower and can spoil a screenshot. Reproduced on a GENUINE native save (SIMTOWER/TOWER5.TDT), so it is a 16-bit Wine-subsystem flake, NOT our export. FIXED THIS SESSION (separate, real harness bugs): run.sh now forwards the SCREEN/MAXIMIZE/ZOOM_CLICKS/CLICK_SECS/SHOT_DELAY/SHOT_OUT env hooks and no longer mounts the host X socket into the headless modes (that mount made the container Xvfb fail to bind, so shots fell back to a blank 1024x768 frame); the image must be rebuilt after entrypoint.sh edits (README noted). The residual winevdm crash is Wine-internal; mitigations if revisited: gentler dialog-dismiss (avoid the WineDbg and the aggressive MAXIMIZE title-bar clicks), a retry-on-crash loop, or pinning a known-good Wine version in the image.
Contributor guide
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.
Research direction
Start with tools/simtower/run.sh and entrypoint.sh, then rebuild the image and reproduce the headless load using the genuine SIMTOWER/TOWER5.TDT save. Review the existing dialog-dismiss and MAXIMIZE behavior before choosing a mitigation; done means the watch-only screenshot is no longer spoiled by a winevdm.exe crash dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100