Skip to content

fix(gateway): route local L2 timers to scene extraction#227

Open
RerankerGuo wants to merge 1 commit into
TencentCloud:feat/serverfrom
RerankerGuo:fix/standalone-l2-timer-routing-226
Open

fix(gateway): route local L2 timers to scene extraction#227
RerankerGuo wants to merge 1 commit into
TencentCloud:feat/serverfrom
RerankerGuo:fix/standalone-l2-timer-routing-226

Conversation

@RerankerGuo

Copy link
Copy Markdown
Contributor

Description | 描述

Route standalone LocalStateBackend legacy timers consistently with the Redis timer scanner:

  • L2_schedule now enqueues a normal L2 task so scene extraction runs.
  • L1_idle now enqueues a normal L1 task.
  • Explicit offload-l2:* timers continue to use the offload worker and keep targetMmdFile extraction.

The local timer parsing is extracted into a small helper with regression tests.

Related Issue | 关联 Issue

Fix #226

Change Type | 修改类型

  • Bug fix | Bug 修复
  • New feature | 新功能
  • Documentation update | 文档更新
  • Code optimization | 代码优化

Self-test Checklist | 自测清单

  • Verified locally | 本地验证通过
  • No existing features affected | 无影响现有功能

Additional Notes | 其他说明

Verified with Node v24.15.0:

  • npm test -- src/gateway/timer-routing.test.ts
  • npm test
  • npm run build

Signed-off-by: Ziyang Guo <121015044+RerankerGuo@users.noreply.github.com>
@Maxwell-Code07

Copy link
Copy Markdown
Collaborator

Thanks for the quick follow-up fix to #226! The timer routing logic is now consistent between standalone and Redis modes. We'll review shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants