概述 Descriptions

修复 LimiterFileSystem 中 open() 方法未对初始网络请求应用速率限制的问题。解决与 fix/cloud-sync 分支的合并冲突。

Fixes open() method in LimiterFileSystem not applying rate limiting to initial network requests. Resolves merge conflicts with fix/cloud-sync branch.

变更内容 Changes

合并冲突解决 Merge Conflict Resolution

成功合并 fix/cloud-sync 分支，该分支已对 openDir() 和 create() 方法应用了速率限制。合并后，确保所有三个方法使用一致的实现模式。

Successfully merged fix/cloud-sync branch which already applied rate limiting to openDir() and create() methods. After merge, all three methods use consistent implementation pattern.

核心修复 Core Fix

将 open() 方法的整个函数体包装在 limiter.execute() 中，与 openDir() 和 create() 使用相同的模式：

Wraps entire open() method body in limiter.execute(), using the same pattern as openDir() and create():

// 修复前 Before
async open(file: File): Promise<FileReader> {
  const reader = await this.fs.open(file);  // 未限速
  return { read: (type) => this.limiter.execute(() => reader.read(type)) };
}

// 修复后 After
async open(file: File): Promise<FileReader> {
  return this.limiter.execute(async () => {
    const reader = await this.fs.open(file);  // 已限速
    return { read: (type) => this.limiter.execute(() => reader.read(type)) };
  });
}

影响范围 Scope

• open() - 文件打开操作现在受速率限制（本 PR 新增）
• openDir() - 目录访问操作受速率限制（已在基础分支中修复）
• create() - 文件创建操作受速率限制（已在基础分支中修复）

确保所有云存储网络请求（Dropbox、OneDrive、Google Drive、WebDAV 等）都通过速率限制器，防止并发过载和服务器限流。

Ensures all cloud storage network requests (Dropbox, OneDrive, Google Drive, WebDAV, etc.) go through the rate limiter to prevent concurrent overload and server throttling.

截图 Screenshots

N/A - 后端逻辑修复，无界面变更 Backend logic fix, no UI changes.

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.