0c9b8f8f1a
- The Activate button also stays disabled while a deactivation runs (selectCanActivate): an activation racing the deactivation after a 409 could reach the server first, clear the machine-limit message and leave the next click to a 429. - activate_body builds the activation request and omits machine_name when the host name is unreadable; the server answers 400 invalid_input to a null. A pure test pins it. - A deactivation whose 2xx body cannot be read stays an invalid_response. Counting it as a success would make the command delete this machine's local token for nothing. A mock-server test pins it. Proven red on the fixed tree: Activate live during a deactivation 1, machine_name sent as null 1, unreadable 2xx body read as empty 1. The same review found that maximus-api answers 500 to the reactivation of a machine deactivated before (unique constraint without is_active): tracked in maximus/maximus-api#70, outside this PR. Refs #270 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| capabilities | ||
| icons | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| tauri.conf.json | ||