feat: migrate mihomo to use kode-bridge IPC on Windows and Unix (#4051)

* Refactor Mihomo API integration and remove crate_mihomo_api

- Removed the `mihomo_api` crate and its dependencies from the project.
- Introduced `IpcManager` for handling IPC communication with Mihomo.
- Implemented IPC methods for managing proxies, connections, and configurations.
- Updated `MihomoManager` to utilize `IpcManager` instead of the removed crate.
- Added platform-specific IPC socket path handling for macOS, Linux, and Windows.
- Cleaned up related tests and configuration files.

* fix: remove duplicate permission entry in desktop capabilities

* refactor: replace MihomoManager with IpcManager and remove Mihomo module

* fix: restore tempfile dependency in dev-dependencies

* fix: update kode-bridge dependency to use git source from the dev branch

* feat: migrate mihomo to use kode-bridge IPC on Windows

This commit implements a comprehensive migration from legacy service IPC to the kode-bridge library for Windows IPC communication. Key changes include:

Replace service_ipc with kode-bridge IpcManager for all mihomo communications
Simplify proxy commands using new caching mechanism with ProxyRequestCache
Add Windows named pipe (\.\pipe\mihomo) and Unix socket IPC endpoint configuration
Update Tauri permissions and dependencies (dashmap, tauri-plugin-notification)
Add IPC logging support and improve error handling
Fix Windows IPC path handling in directory utilities
This migration enables better cross-platform IPC support and improved performance for mihomo proxy core communication.

* doc: add IPC communication with Mihomo kernel, removing Restful API dependency

* fix: standardize logging type naming from IPC to Ipc for consistency

* refactor: clean up and optimize code structure across multiple components and services

- Removed unnecessary comments and whitespace in various files.
- Improved code readability and maintainability by restructuring functions and components.
- Updated localization files for consistency and accuracy.
- Enhanced performance by optimizing hooks and utility functions.
- General code cleanup in settings, pages, and services to adhere to best practices.

* fix: simplify URL formatting in test_proxy_delay method

* fix: update kode-bridge dependency to version 0.1.3 and change source to crates.io

* fix: update macOS target versions in development workflow

* Revert "fix: update macOS target versions in development workflow"

This reverts commit b9831357e462e0f308d11a9a53cb718f98ae1295.

* feat: enhance IPC path handling for Unix systems and improve directory safety checks

* feat: add conditional compilation for Unix-specific IPC path handling

* chore: update cagro.lock

* feat: add external controller configuration and UI support

* Refactor proxy and connection management to use IPC-based commands

- Updated `get_proxies` function in `proxy.rs` to call the new IPC command.
- Renamed `get_refresh_proxies` to `get_proxies` in `ipc/general.rs` for consistency.
- Added new IPC commands for managing proxies, connections, and configurations in `cmds.ts`.
- Refactored API calls in various components to use the new IPC commands instead of HTTP requests.
- Improved error handling and response management in the new IPC functions.
- Cleaned up unused API functions in `api.ts` and redirected relevant calls to `cmds.ts`.
- Enhanced connection management features including health checks and updates for proxy providers.

* chore: update dependencies and improve error handling in IPC manager

* fix: downgrade zip dependency from 4.3.0 to 4.2.0

* feat: Implement traffic and memory data monitoring service

- Added `TrafficService` and `TrafficManager` to manage traffic and memory data collection.
- Introduced commands to get traffic and memory data, start and stop the traffic service.
- Integrated IPC calls for traffic and memory data retrieval in the frontend.
- Updated `AppDataProvider` and `EnhancedTrafficStats` components to utilize new data fetching methods.
- Removed WebSocket connections for traffic and memory data, replaced with IPC polling.
- Added logging for better traceability of data fetching and service status.

* refactor: unify external controller handling and improve IPC path resolution

* fix: replace direct IPC path retrieval with guard function for external controller

* fix: convert external controller IPC path to string for proper insertion in config map

* fix: update dependencies and improve IPC response handling

* fix: remove unnecessary unix conditional for ipc path import

* Refactor traffic and memory monitoring to use IPC stream; remove TrafficService and TrafficManager. Introduce new IPC-based data retrieval methods for traffic and memory, including formatted data and system overview. Update frontend components to utilize new APIs for enhanced data display and management.

* chore: bump crate rand version to 0.9.2

* feat: Implement enhanced traffic monitoring system with data compression and sampling

- Introduced `useTrafficMonitorEnhanced` hook for advanced traffic data management.
- Added `TrafficDataSampler` class for handling raw and compressed traffic data.
- Implemented reference counting to manage data collection based on component usage.
- Enhanced data validation with `SystemMonitorValidator` for API responses.
- Created diagnostic tools for monitoring performance and error tracking.
- Updated existing hooks to utilize the new enhanced monitoring features.
- Added utility functions for generating and formatting diagnostic reports.

* feat(ipc): improve URL encoding and error handling for IPC requests

- Add percent-encoding for URL paths to handle special characters properly
- Enhance error handling in update_proxy with proper logging
- Remove excessive debug logging to reduce noise
- Update kode-bridge dependency to v0.1.5
- Fix JSON parsing error handling in PUT requests

Changes include:
- Proper URL encoding for connection IDs, proxy names, and test URLs
- Enhanced error handling with fallback responses in updateProxy
- Comment out verbose debug logs in traffic monitoring and data validation
- Update dependency version for improved IPC functionality

* feat: major improvements in architecture, traffic monitoring, and data validation

* Refactor traffic graph components: Replace EnhancedTrafficGraph with EnhancedCanvasTrafficGraph, improve rendering performance, and enhance visual elements. Remove deprecated code and ensure compatibility with global data management.

* chore: update UPDATELOG.md for v2.4.0 release, refine traffic monitoring system details, and enhance IPC functionality

* chore: update UPDATELOG.md to reflect removal of deprecated MihomoManager and unify IPC control

* refactor: remove global traffic service testing method from cmds.ts

* Update src/components/home/enhanced-canvas-traffic-graph.tsx

* Update src/hooks/use-traffic-monitor-enhanced.ts

* Update src/components/layout/layout-traffic.tsx

* refactor: remove debug state management from LayoutTraffic component

---------
This commit is contained in:
Tunglies
2025-07-24 00:47:42 +08:00
committed by Tunglies
parent f580409ade
commit 15a1770ee9
62 changed files with 4029 additions and 1762 deletions

230
src/utils/data-validator.ts Normal file
View File

@@ -0,0 +1,230 @@
/**
* 类型安全的数据验证器
* 确保从后端接收的数据符合预期的接口定义
*/
// 数字验证器
function isValidNumber(value: any): value is number {
return typeof value === "number" && !isNaN(value) && isFinite(value);
}
// 字符串验证器
function isValidString(value: any): value is string {
return typeof value === "string" && value.length > 0;
}
// 布尔值验证器
function isValidBoolean(value: any): value is boolean {
return typeof value === "boolean";
}
/**
* 系统监控数据验证器
*/
export class SystemMonitorValidator implements ISystemMonitorOverviewValidator {
/**
* 验证数据是否符合ISystemMonitorOverview接口
*/
validate(data: any): data is ISystemMonitorOverview {
if (!data || typeof data !== "object") {
console.warn("[DataValidator] 数据不是对象:", data);
return false;
}
// 验证traffic字段
if (!this.validateTrafficData(data.traffic)) {
console.warn("[DataValidator] traffic字段验证失败:", data.traffic);
return false;
}
// 验证memory字段
if (!this.validateMemoryData(data.memory)) {
console.warn("[DataValidator] memory字段验证失败:", data.memory);
return false;
}
// 验证overall_status字段
if (!this.validateOverallStatus(data.overall_status)) {
console.warn(
"[DataValidator] overall_status字段验证失败:",
data.overall_status,
);
return false;
}
return true;
}
/**
* 清理和修复数据确保返回有效的ISystemMonitorOverview
*/
sanitize(data: any): ISystemMonitorOverview {
// console.log("[DataValidator] 开始数据清理:", data);
const sanitized: ISystemMonitorOverview = {
traffic: this.sanitizeTrafficData(data?.traffic),
memory: this.sanitizeMemoryData(data?.memory),
overall_status: this.sanitizeOverallStatus(data?.overall_status),
};
// console.log("[DataValidator] 数据清理完成:", sanitized);
return sanitized;
}
private validateTrafficData(traffic: any): boolean {
if (!traffic || typeof traffic !== "object") return false;
// 验证raw字段
const raw = traffic.raw;
if (!raw || typeof raw !== "object") return false;
if (
!isValidNumber(raw.up) ||
!isValidNumber(raw.down) ||
!isValidNumber(raw.up_rate) ||
!isValidNumber(raw.down_rate)
) {
return false;
}
// 验证formatted字段
const formatted = traffic.formatted;
if (!formatted || typeof formatted !== "object") return false;
if (
!isValidString(formatted.up_rate) ||
!isValidString(formatted.down_rate) ||
!isValidString(formatted.total_up) ||
!isValidString(formatted.total_down)
) {
return false;
}
// 验证is_fresh字段
if (!isValidBoolean(traffic.is_fresh)) return false;
return true;
}
private validateMemoryData(memory: any): boolean {
if (!memory || typeof memory !== "object") return false;
// 验证raw字段
const raw = memory.raw;
if (!raw || typeof raw !== "object") return false;
if (
!isValidNumber(raw.inuse) ||
!isValidNumber(raw.oslimit) ||
!isValidNumber(raw.usage_percent)
) {
return false;
}
// 验证formatted字段
const formatted = memory.formatted;
if (!formatted || typeof formatted !== "object") return false;
if (
!isValidString(formatted.inuse) ||
!isValidString(formatted.oslimit) ||
!isValidNumber(formatted.usage_percent)
) {
return false;
}
// 验证is_fresh字段
if (!isValidBoolean(memory.is_fresh)) return false;
return true;
}
private validateOverallStatus(status: any): boolean {
return (
typeof status === "string" &&
["active", "inactive", "error", "unknown"].includes(status)
);
}
private sanitizeTrafficData(traffic: any) {
const raw = traffic?.raw || {};
const formatted = traffic?.formatted || {};
return {
raw: {
up: isValidNumber(raw.up) ? raw.up : 0,
down: isValidNumber(raw.down) ? raw.down : 0,
up_rate: isValidNumber(raw.up_rate) ? raw.up_rate : 0,
down_rate: isValidNumber(raw.down_rate) ? raw.down_rate : 0,
},
formatted: {
up_rate: isValidString(formatted.up_rate) ? formatted.up_rate : "0B",
down_rate: isValidString(formatted.down_rate)
? formatted.down_rate
: "0B",
total_up: isValidString(formatted.total_up) ? formatted.total_up : "0B",
total_down: isValidString(formatted.total_down)
? formatted.total_down
: "0B",
},
is_fresh: isValidBoolean(traffic?.is_fresh) ? traffic.is_fresh : false,
};
}
private sanitizeMemoryData(memory: any) {
const raw = memory?.raw || {};
const formatted = memory?.formatted || {};
return {
raw: {
inuse: isValidNumber(raw.inuse) ? raw.inuse : 0,
oslimit: isValidNumber(raw.oslimit) ? raw.oslimit : 0,
usage_percent: isValidNumber(raw.usage_percent) ? raw.usage_percent : 0,
},
formatted: {
inuse: isValidString(formatted.inuse) ? formatted.inuse : "0B",
oslimit: isValidString(formatted.oslimit) ? formatted.oslimit : "0B",
usage_percent: isValidNumber(formatted.usage_percent)
? formatted.usage_percent
: 0,
},
is_fresh: isValidBoolean(memory?.is_fresh) ? memory.is_fresh : false,
};
}
private sanitizeOverallStatus(
status: any,
): "active" | "inactive" | "error" | "unknown" {
if (
typeof status === "string" &&
["active", "inactive", "error", "unknown"].includes(status)
) {
return status as "active" | "inactive" | "error" | "unknown";
}
return "unknown";
}
}
// 全局验证器实例
export const systemMonitorValidator = new SystemMonitorValidator();
/**
* 安全的API调用包装器
*/
export function withDataValidation<T extends (...args: any[]) => Promise<any>>(
apiCall: T,
validator: { validate: (data: any) => boolean; sanitize: (data: any) => any },
): T {
return (async (...args: Parameters<T>) => {
try {
const result = await apiCall(...args);
if (validator.validate(result)) {
return result;
} else {
console.warn("[DataValidator] API返回数据验证失败尝试修复:", result);
return validator.sanitize(result);
}
} catch (error) {
console.error("[DataValidator] API调用失败:", error);
// 返回安全的默认值
return validator.sanitize(null);
}
}) as T;
}