When the server answers 400 to a restore or a removal, the Snapshot Manager built its message from target.title and exception. target is the snapshot's name, a string, and exception is not defined at that point, so the line threw and the catch block showed "Restore snapshot failed: undefined / ReferenceError: exception is not defined", for a removal too. The finally block of the restore then asked for a restart, although nothing had been scheduled. Any other error status, such as a 502 from a proxy, was taken as success. - Show the snapshot's name and the reason, both escaped. The reason is the text of a plain-text response, which is how the server gives one, and otherwise the status line: most of the server's refusals carry no text, and a proxy answers with an HTML page - Handle every error status this way, where only 400 was looked at - Return after a failure, and ask for a restart only when the restore was accepted - Name the removal in the removal's messages - Add Playwright cases for a failed restore and removal, answered with 400 with and without a reason and with the 502 page of a proxy, for a restore refused with 403, and for an accepted restore - Add a CHANGELOG entry and name the cases in the Playwright README The same change for main is #3436.
ComfyUI-Manager: Frontend (js)
This directory contains the JavaScript frontend implementation for ComfyUI-Manager, providing the user interface components that interact with the backend API.
Core Components
- comfyui-manager.js: Main entry point that initializes the manager UI and integrates with ComfyUI.
- custom-nodes-manager.js: Implements the UI for browsing, installing, and managing custom nodes.
- model-manager.js: Handles the model management interface for downloading and organizing AI models.
- components-manager.js: Manages reusable workflow components system.
- snapshot.js: Implements the snapshot system for backing up and restoring installations.
Sharing Components
- comfyui-share-common.js: Base functionality for workflow sharing features.
- comfyui-share-youml.js: Integration with the YouML sharing platform.
Utility Components
- cm-api.js: Client-side API wrapper for communication with the backend.
- common.js: Shared utilities and helper functions used across the frontend.
- node_fixer.js: Utilities for fixing disconnected links and repairing malformed nodes by recreating them while preserving connections.
- popover-helper.js: UI component for popup tooltips and contextual information.
- turbogrid.esm.js: Grid component library - https://github.com/cenfun/turbogrid
- workflow-metadata.js: Handles workflow metadata parsing, validation and cross-repository compatibility including versioning, dependencies tracking, and resource management.
Architecture
The frontend follows a modular component-based architecture:
- Integration Layer: Connects with ComfyUI's existing UI system
- Manager Components: Individual functional UI components (node manager, model manager, etc.)
- Sharing Components: Platform-specific sharing implementations
- Utility Layer: Reusable UI components and helpers
Implementation Details
- The frontend integrates directly with ComfyUI's UI system through
app.js - Dialog-based UI for most manager functions to avoid cluttering the main interface
- Asynchronous API calls to handle backend operations without blocking the UI
Styling
CSS files are included for specific components:
- custom-nodes-manager.css: Styling for the node management UI
- model-manager.css: Styling for the model management UI
This frontend implementation provides a comprehensive yet user-friendly interface for managing the ComfyUI ecosystem.