[BUG]: Contributor profile bypasses the shared cache and rate-limit handling

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

维护者通常 1 天内回复

@sumitsingh-cyber 已经在做这个了。

开始于 2026年11月14日。

  • #455 来自 @sumitsingh-cyber —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
57/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, javascript

调研方向

Find the contributor profile code that makes the direct fetch call and compare it with the shared fetchWithCache service. Read how fetchAllPages handles 403 responses and whether it handles 429; the issue gives no file or test names, so locate these entry points in the repository. Done means repeated views use the shared cache and rate-limit handling.

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

描述

bug
Bug Description

Contributor profile data is fetched with a direct fetch call instead of the shared fetchWithCache service. This bypasses the IndexedDB cache and the repo-wide rate-limit rules. fetchAllPages treats every 403 as RATE_LIMIT and does not handle 429 explicitly.

Every profile view spends GitHub Search API quota, even when the same contributor was viewed moments earlier.

Steps to Reproduce
  1. Open a contributor profile.
  2. Navigate away and return to the same profile.
  3. Observe new GitHub Search API requests in DevTools instead of a cache hit.
  4. Repeat until the search rate limit is reached.
Impact

Low - Minor inconvenience

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
主要语言
JavaScript
星标
53
派生
182
平均合并
18 分钟
30 天内合并 PR
2

环境准备

从这里开始

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

AOSSIE-Org/OrgExplorer 的其他 Issue

查看 AOSSIE-Org/OrgExplorer 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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