Skip to content

Add config_lock and fix multiple frontend issues - #270

Merged
thomas9120 merged 3 commits into
mainfrom
beta
Jul 29, 2026
Merged

Add config_lock and fix multiple frontend issues#270
thomas9120 merged 3 commits into
mainfrom
beta

Conversation

@thomas9120

Copy link
Copy Markdown
Owner

No description provided.

Introduce config_lock on ServerState and serialize load→mutate→save cycles in llama_manager, external_server, process_manager and hf_download to prevent races. Other fixes: activate_custom now claims/releases the install slot; sanitize_sse_error always logs the error; chat proxy parsing skips malformed addresses; macOS file picker returns a cancel sentinel; HF download rejects Windows device names and correctly reports 0-byte size_mb and logs partial-delete failures; lifecycle validates folder input before mkdir; startup script validates port and preserves browser errors. Tests updated/added.
Various frontend robustness and correctness fixes: guard stale responses in manager.refreshModels; log errors in waitForServerReady; include model flags and chat-template warning in flag-core; guard API key selection and server-ready text in api-tab; use shared hasLaunchModelArg in app.js; add searchable-select.destroy; avoid clobbering external-server inputs and improve disconnect badge; remove unused benchmark timer; make presets use a null-prototype map and harden import loop; protect process-lifecycle initial emit. Tests: add model-cache race test and fix remote_tunnel toggle stub.
@thomas9120 thomas9120 self-assigned this Jul 29, 2026
@thomas9120
thomas9120 marked this pull request as ready for review July 29, 2026 23:54
@thomas9120
thomas9120 merged commit 17047e9 into main Jul 29, 2026
5 checks passed
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.

1 participant