Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Five console tests each wait up to a minute of wall clock for a usage minute to close

未关闭
#865 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
playwright, typescript

调研方向

Read e2e/console/overview.spec.ts and e2e/console/usage.spec.ts, focusing on scriptedRun and the five listed call sites. Trace how /v1/stats exposes closed minutes, then compare sharing a scripted run per file with another way to close a minute. Done when the five tests retain their coverage and the console lane no longer waits for each wall-clock minute to close.

由索引模型根据 Issue 内容生成。

描述

bug:new

scriptedRun in e2e/console/overview.spec.ts:61-80 and e2e/console/usage.spec.ts:65-84 waits until the wall-clock minute the run started in is over (minuteOver, lines 71-72 and 78-79), because /v1/stats charts closed minutes only. Five tests call it: overview.spec.ts:123, :153, :174, :282 and usage.spec.ts:131.

They are about a quarter of the console lane's test time, in every browser:

CI main 1680c5c1, Chromium:  54.4 s, 59.3 s, 1.1 min, 41.5 s, 49.0 s  = ~270 s of 976 s
local main, Chromium:        45.1 s, 59.8 s, 1.1 min, 48.4 s, 22.4 s

They arrived with #626, the first main run whose Console job timed out (60521f0f). Sharing one scripted run per file, or a way to close a minute without waiting, would cut most of it.

Found while triaging #852.

Written by an agent.

主要语言
TypeScript
星标
20
派生
2
平均合并
8 小时 8 分钟
30 天内合并 PR
366

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。