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

Killed instance | Failed function invocation

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the /api/registry/timeline/sizes/next endpoint and the loader used by the timeline pages; the report says the failure also affected Next and Vite timeline pages. Compare server logs and behavior on failing requests versus reloads, focusing on why an invocation is killed and the loader hides the failure. Done means the intermittent failure is understood and users are not shown an apparently successful empty result when it occurs.

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

描述

When loading the timeline/package/changelog pages - in some cases vercel kills current instance.

Caught for example on next and vite timeline pages.
At the same time the loader just hides and to the user it appears as if everything was fine and just nothing was found. The interface looks correct and overall does not interfere with the experience.

For timeline page it only happened with /sizes/

Error:

Image

Server logs (/api/registry/timeline/sizes/next)

Image

After a reload, it usually works. That is, most likely, some of the logic was processed and cached, but post-processing failed. Perhaps there's a memory leak somewhere.

It seems to occur in about 1 request per 10000-100000

主要语言
TypeScript
星标
3.6k
派生
533
平均合并
4 天 13 小时
30 天内合并 PR
37

环境准备

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

从这里开始

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

npmx-dev/npmx.dev 的其他 Issue

查看 npmx-dev/npmx.dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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