PR #49658: fix(feishu): convert absolute paths to file:// URLs for ESM imports on Windows

• Repository: openclaw/openclaw
• Author: ayushozha
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49658

Description (problem / solution / changelog)

Summary

• Convert dynamic import() calls in the Feishu extension to use new URL(specifier, import.meta.url).href, ensuring the resolved import URL always uses the file:// scheme on Windows.
• On Windows, Node.js ESM loader rejects absolute paths (e.g. g:\...) passed to import() because the drive letter is interpreted as a URL scheme. Resolving relative specifiers against import.meta.url produces proper file:// URLs that work cross-platform.
• Affects two dynamic imports in extensions/feishu/src/channel.ts: the lazy channel runtime loader and the gateway startAccount monitor import.

Fixes #49489

Note

Other extensions (matrix, msteams, telegram, zalouser, bluebubbles, googlechat, tlon, zalo, imessage) have the same import("./...") pattern in their channel.ts files. Those should be updated in a follow-up for consistency, though this PR focuses on the Feishu extension as reported in the issue.

Test plan

• All 43 Feishu test files pass (461 tests)
• Verify on Windows that the Feishu channel starts without ESM loader errors

🤖 Generated with Claude Code

Changed files

• extensions/feishu/src/channel.ts (modified, +4/-2)

PR #43043: fix(channels): resolve log file path for cross-date Gateway runs

• Repository: openclaw/openclaw
• Author: wdskuki
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/43043

Description (problem / solution / changelog)

Summary

Fixes #42875

When Gateway runs across date boundaries, the log file is created based on the startup date (e.g., openclaw-2026-03-10.log). However, the CLI command openclaw channels logs was using getResolvedLoggerSettings().file which returns the current date'''s log file (e.g., openclaw-2026-03-11.log), causing users to see empty or stale logs.

Changes

Added a resolveLogFile() function to src/commands/channels/logs.ts that:

1. Returns the configured file if it exists
2. For rolling log files (openclaw-YYYY-MM-DD.log), finds the most recent log file by mtime in the same directory
3. Falls back to the configured file if no rolling logs are found

This mirrors the behavior already implemented in the Gateway'''s logs.tail handler (src/gateway/server-methods/logs.ts), ensuring consistent log file resolution across CLI and Gateway.

Testing

Added comprehensive tests in src/commands/channels/logs.test.ts covering:

• Resolving to most recent log file when current date file does not exist
• Using current date file when it exists
• Selecting most recent file by mtime when multiple exist
• Channel filtering
• Empty log directory handling
• Non-rolling log file paths

Checklist

• Bug fix
• Tests added
• Backward compatible
• No breaking changes

Changed files

• src/commands/channels/logs.test.ts (added, +216/-0)
• src/commands/channels/logs.ts (modified, +38/-1)