Skip to content

Fix event loop handling in ConfigApp to ensure proper closure - #1028

Merged
PCMan merged 1 commit into
EasyIME:masterfrom
leon728:fix/issue-1027-config_process_not_terminated
Nov 8, 2026
Merged

PCMan merged 1 commit into
EasyIME:masterfrom
leon728:fix/issue-1027-config_process_not_terminated

Conversation

@leon728

@leon728 leon728 commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Fix #1027

Soluion:
As described in the issue.

Validation:
config_tool.py backend process terminated after 120s timeout.

@PCMan
PCMan merged commit e7306ec into EasyIME:master Nov 8, 2026
1 check passed
@PCMan PCMan self-assigned this Nov 8, 2026
asdf80730 added a commit to asdf80730/PIME that referenced this pull request Nov 11, 2026
Brings the four merged upstream threads onto the integration ref: the
launcher watchdog pending-request purge (EasyIME#1002), the shared librime
instance kept alive across the session lifecycle (EasyIME#1003), the Windows 10
installer floor (EasyIME#1005) and the ConfigApp event-loop closure (EasyIME#1028).
The one conflict, in the launcher restart loop, keeps the outer
pending_requests map and the per-retry clear that upstream introduced.

Fully generated by omp (Qwen3.8-Flash-Next) without human intervention.
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.

config_tool.py keep running even after config web page is closed

2 participants