No description
The Close() function was incorrectly setting s.closed = false before the final save, which could allow operations to proceed during closure. Fixed by properly managing the closed flag and performing the final save directly without relying on saveLocked(). This fixes the virtual node state management implementation which provides: - Node creation at specified positions with bounds validation - State persistence to disk via JSON - Thread-safe operations with mutex locking - Enable/disable, position updates, role changes, metadata, tags Acceptance criteria met: - Nodes can be created at specified positions - Nodes maintain their state within the virtual space Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .beads | ||
| .github/workflows | ||
| .marathon | ||
| dashboard | ||
| docs | ||
| firmware | ||
| mothership | ||
| tests/e2e | ||
| .dockerignore | ||
| .gitignore | ||
| .needle-predispatch-sha | ||
| .needle.yaml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| PROGRESS.md | ||
| VERSION | ||