nikon/Codesys-MCP-SP21-plus
0
0
Fork 0
Code Activity Actions

docs(function-test): close severity-bitmask repro todo, note round-trip still deferred

Browse source 
- Severity-bitmask long crash repro confirmed end-to-end via SymTest.project
  (PLCWinNT, device not installed -> 17 ERROR messages, 2 WARNING, 34 total
  through get_compile_messages with _coerce_for_json -- no TypeError).
- MCPTest2/Application/Symbols cleanup recorded.
- 5 deferred symbol-config tools still pending a build-clean project.
This commit is contained in:
Karstein Phobic Nyvold Kvistad 2026-04-29 09:34:54 +02:00
parent e0a4685c11
commit 0fdb0046d8
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/function-test-2026-04-28.md
View file

@ -120,4 +120,6 @@ The plan also calls out the `SymbolAccess` enum-value probe risk: the SP22 stub
- **Crash pattern.** Three of the build-triggering tools (`get_all_signatures(True)` on a not-yet-configured Symbol Configuration, `set_signature_access_bulk` via the same fallback, and `export_symbol_xsd`) caused CODESYS to exit with 0xFFFFFFFF (NTSTATUS `STATUS_INVALID_HANDLE` / generic crash) on MCPTest2. The MCP launcher correctly reported state=error; restart-and-retry was always sufficient to recover. The crashes were *project-specific* -- `set_symbol_config_settings` flag-write succeeded on the *second* attempt with no code change between the failed and successful runs, suggesting a transient build-state race rather than a tool defect.
- **Wrapper message fix landed in `e948922`.** `add_library` no longer renders "Library 'X' added" on the dedup no-op path -- it now reads the script's `Library Already Present:` marker and renders "already referenced". Cosmetic todo from this doc closed.
- **Session ledger** (per `feedback_session_ledger.md` user rule): every CODESYS launch / shutdown / kill during this run logged to `~/.claude/projects/<id>/state/session_ledger.jsonl` so a next session knows which CODESYS.exe PIDs are mine to reclaim.
- **Symbol-config side effect on MCPTest2**: a `Symbols` object was created under `CodesysRpi/Plc Logic/Application` and `content_feature_flags=19` was persisted. `git restore` the `.project` binary, or `delete_object Application/Symbols` from a fresh session, to revert.
- **Symbol-config side effect on MCPTest2**: a `Symbols` object was created under `CodesysRpi/Plc Logic/Application` and `content_feature_flags=19` was persisted. Cleaned up 2026-04-29: `delete_object Application/Symbols` succeeded, project saved.
- **Severity-bitmask `long` repro confirmed (todo from 2026-04-28 closed).** Created a fresh `SymTest.project` from the Standard template (PLCWinNT device, not installed). `compile_project` returned 17 ERROR-severity messages and 2 WARNING; `get_compile_messages` then surfaced 34 total messages (17 ERROR + 2 WARNING + 15 INFO/TEXT) via the `_coerce_for_json` walker with **no** `TypeError: <N>L is not JSON serializable`. The Severity-bitmask `long` -> `int`/`str` coercion fix in `763a307` is now end-to-end-verified against real compile errors, not just an empty-message non-regression run. SymTest left in place for future re-runs.
- **Round-trip remainder (todo 3, 5 tools) still deferred.** Both available projects build dirty: MCPTest2 (CodesysRpi target) crashes the build via IoDrvGPIO managed library; SymTest (PLCWinNT) reports the device as not-installed. The 5 build-triggering tools (`list_all_signatures`, `list_all_datatypes`, `set_symbol_access` fallback path, `set_signature_access_bulk`, `export_symbol_xsd`) need a project that builds clean headless. Suggest creating a project against an installed soft-PLC target (e.g. CODESYS Control Win V3 if installed) for the next pass.