BUG: Open editor requests return 502 during local server restart #256

New issue

Open

opened 2026-09-27 18:07:22 +00:00 by kayg · 3 comments

kayg commented

2026-09-27 18:07:22 +00:00

Owner

Finding

The adversarial editor probe recorded HTTP 502 responses during a planned local server restart with a live Note open.

The browser logged 502 for GET /api/v1/files/entries?path=Notes, GET /api/v1/notes, the Note backlinks endpoint and GET /api/v1/search. The edit marker later persisted exactly once, and the server stayed alive. The restart handshake completed, so this was not the runner missing its restart request.

Please confirm the expected client behavior during the restart window. Add a real-server regression check for requests made by an open editor across restart, and retry or avoid exposing transient 502s if the API contract requires it.

Probe: tests/adversarial/editor.mjs, live editor restart area. The round ran on job/fonts after merging dev at ac941215.

## Finding The adversarial editor probe recorded HTTP 502 responses during a planned local server restart with a live Note open. The browser logged 502 for `GET /api/v1/files/entries?path=Notes`, `GET /api/v1/notes`, the Note backlinks endpoint and `GET /api/v1/search`. The edit marker later persisted exactly once, and the server stayed alive. The restart handshake completed, so this was not the runner missing its restart request. Please confirm the expected client behavior during the restart window. Add a real-server regression check for requests made by an open editor across restart, and retry or avoid exposing transient 502s if the API contract requires it. Probe: `tests/adversarial/editor.mjs`, live editor restart area. The round ran on `job/fonts` after merging `dev` at `ac941215`.

kayg referenced this issue

2026-09-27 18:58:46 +00:00

UI: Google Sans default + configurable fonts in Settings → Appearance #234

kayg commented

2026-10-02 17:02:43 +00:00

Author

Owner

Duplicate candidate: #260 covers the same restart window, endpoints and transient 502 responses described here. It also states the expected bounded retry and reconnect behavior and a real-server regression. Recommend linking this evidence to #260 and keeping #260 as the tracking issue; do not close either issue as part of this audit.

kayg referenced this issue

2026-10-02 17:02:51 +00:00

EDITOR: open editor gets transient 502s during a server restart #260

kayg referenced this issue

2026-10-02 17:42:29 +00:00

Audit: open issue hygiene (duplicates, already fixed, stale) #866

kayg commented

2026-10-03 11:55:44 +00:00

Author

Owner

Duplicate of #260: both report the same transient editor 502 during server restart. Keep #260 as the active tracker.

kayg closed this issue

2026-10-03 11:55:44 +00:00

kayg referenced this issue

2026-10-03 12:04:41 +00:00

Issue hygiene sweep 2026-10-03 #1008

kayg commented

2026-10-03 12:14:15 +00:00

Author

Owner

Correction to the issue-hygiene disposition: this issue carries explicit OPEN and LATER markers, so it must remain open under the sweep rules. The earlier duplicate disposition was too aggressive. Reopening and leaving it for the owner to reclassify.

kayg reopened this issue

2026-10-03 12:14:23 +00:00

kayg referenced this issue

2026-10-03 12:15:37 +00:00

Moving in by dropping Markdown folders: find and fix what breaks (replaces the dedicated importer) #719

kayg referenced this issue

2026-10-03 12:56:40 +00:00

Issue hygiene sweep 2026-10-03 #1008